RE: [ECOS] newer version of Windows configuration tool

["Gary Stebbins" <GStebbins at bruxton dot com>]

Thanks for the quick response. The new tool did generate the /ecos-x
filenames in most cases, but missed a few! I thought about editing the
files, but also realized I would need to do that every time I did a
build. Being UNIX naïve, it would take me a while to create a script to
automatically do this (which I would need to do to give to a customer). 

I'm using the MFC tool. Is there an equivalent to the 'ecosconfig tree',
or can I execute that from the command line, then continue to use the
MFC tool?

Thanks!

Gary

-----Original Message-----
From: Gokhan Tanyeri [mailto:gokhan@clarinox.com] 
Sent: Monday, December 03, 2001 6:09 PM
To: Gary Stebbins; ecos-discuss@sources.redhat.com
Cc: julians@redhat.com
Subject: RE: [ECOS] newer version of Windows configuration tool 
Importance: High


At 01:34 PM 11/27/01 +1100, Gokhan Tanyeri wrote:
 >A simple workaround for this one is to replace //C with /C in your
>"makefile"s (around 10-15 of them!!). works fine ;) The trouble is
everytime  >you try to build something you need to go through this
global search and  >replace.

The new ecosconfig and configtools really should generate working
filenames -- prefixed by /ecos-x, where x is a DOS drive letter -- so if
you uploaded the new tools and are still having the problem, you maybe
forgot to go 'ecosconfig tree' again.

The updated MFC configtool.exe and command-line ecosconfig.exe binaries
are
here:

ftp://sources.redhat.com/pub/ecos/anoncvs/ct-update-011025.zip

The latest Configtool 2 distribution for Windows is here:


->-----Original Message-----
->From: ecos-discuss-owner@sources.redhat.com
->[mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Gary 
->Stebbins
->Sent: Tuesday, 4 December 2001 12:55
->To: ecos-discuss@sources.redhat.com
->Cc: julians@redhat.com
->Subject: Re: [ECOS] newer version of Windows configuration tool
->
->
->>From an older discussion of 26-Oct-2001 Julian Smart wrote:
->>>>That depends on what Cygwin you have installed (CT 1 doesn't cope
->with the
->path conventions of newer versions of Cygwin), but I have zipped up a 
->modified CT 1 (and ecosconfig.exe) which will make their way to the 
->ftp site very shortly.<<<
->
->I have the new Cygwin installed, and am having problems with the 
->configuration tool, "eCos Configuration Tool, 1.3.net, Oct 10 2001 
->14:39:51".
->
->Is there still a problem with the configuration tool (old-style path 
->generated), or do I need to update something in addition to replacing 
->the old configuration tool with the new? Any help appreciated. Error 
->log below.
->
->Thank you.
->
->Gary
->
->
->make[1]: Leaving directory 
->`/ecos-c/Current/uITRON/eCOS/eCos_build/compat/uitron/v1_3_1'
->headers finished
->make -r -C hal/arm/arch/v1_3_1 arm.inc
->make[1]: Entering directory 
->`/ecos-c/Current/uITRON/eCOS/eCos_build/hal/arm/arch/v1_3_1'
->make[1]: 
->stat://C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/hal_m
->k_
->defs.c: No such host or network path
->make[1]: *** No rule to make target
->`//C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/hal_mk_de
fs
->.c', needed by `arm.inc'.  Stop.