[ECOS] Re: adding a package with configtool fails
John Dallaway
john@dallaway.org.uk
Sat Mar 9 09:14:00 GMT 2013
Bob
On 08/03/13 11:06, Bob Brusa wrote:
> I moved eCos and tools and the sourcecode of project P2 to a new(er) pc
> (W7). Actually I had already done an eCos-related project P1 on this pc
> and hence, I know that everything is working, but P2 needs a (user
> written) package, not yet included in eCos:
>
> - When adding this package with configtool>Tools>Administration and
> opening the corresponding epk-file, configtool does not report any
> errors, but the added package is still not part of ecos.
>
> When performing this same operation with the same epk-file on the
> previous old PC, it works. There seems to be something missing on my new
> pc. But how to find out what?
I believe this is a regression related to the move to Cygwin tcl8.5
which is a "unix" build and does not understand Windows file paths.
A workaround would be to specify the location of the .epk file using a
POSIX-style file path at a Cygwin bash prompt:
cd /opt/ecos/packages
tclsh ecosadmin.tcl add /home/myUsername/myPackages.epk
Please raise a bug report against ConfigTool in bugzilla:
http://bugs.ecos.sourceware.org/
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss
mailing list