From: John Dallaway <john@dallaway.org.uk>
To: Bob Brusa <bob.brusa@gmail.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: adding a package with configtool fails
Date: Sat, 09 Mar 2013 09:14:00 -0000 [thread overview]
Message-ID: <513AFD6D.6080308@dallaway.org.uk> (raw)
In-Reply-To: <5139C644.1020200@gmail.com>
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
prev parent reply other threads:[~2013-03-09 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 11:06 [ECOS] " Bob Brusa
2013-03-08 12:41 ` Sergei Gavrikov
2013-03-08 14:39 ` Bob Brusa
2013-03-08 18:56 ` Sergei Gavrikov
2013-03-09 9:14 ` John Dallaway [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=513AFD6D.6080308@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=bob.brusa@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).