This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: NASTY bug in eCos ConfigTool 1.3.1.2 Win32
- To: "'Gary Thomas'" <gthomas at cambridge dot redhat dot com>
- Subject: RE: [ECOS] NASTY bug in eCos ConfigTool 1.3.1.2 Win32
- From: "Trenton D. Adams" <tadams at extremeeng dot com>
- Date: Wed, 13 Jun 2001 08:37:18 -0600
- Cc: "'eCos'" <ecos-discuss at sources dot redhat dot com>
- Organization: Extreme Engineering
I was told you can't use the Config Tool 2.0 alpha with the latest CVS
so I haven't bothered to try.
-----Original Message-----
From: gary@chez-thomas.org [mailto:gary@chez-thomas.org] On Behalf Of
Gary Thomas
Sent: Wednesday, June 13, 2001 6:14 AM
To: Trenton D. Adams
Cc: eCos
Subject: RE: [ECOS] NASTY bug in eCos ConfigTool 1.3.1.2 Win32
On 12-Jun-2001 Trenton D. Adams wrote:
> I have two separate configs. The are identical except one is RAM, and
> the other is ROM support for the kernel. If I change from ROM to RAM
> support, it doesn't allow me to save the new configuration under the
> current project. I have to select File|Exit in order for it to ask me
> to save and then it will finally acutally save it. This caused me to
> compile a program thinking it would run in RAM when it was actually
> meant to be run in ROM.
Does this problem exist with the latest (Config Tool 2.0 alpha)?
The old tool is no longer maintained, so the most we can do is make sure
that the problem is fixed in the new one.