From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Bob Brusa <bob.brusa@gmail.com>
Cc: ecos discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] adding a package with configtool fails
Date: Fri, 08 Mar 2013 12:41:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1303081535180.2542@sg-laptop> (raw)
In-Reply-To: <5139C644.1020200@gmail.com>
On Fri, 8 Mar 2013, Bob Brusa wrote:
> Hi,
> 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?
Hi Bob
May be your installation lacks Tcl. Try from cygwin bash prompt
tclsh "${ECOS_REPOSITORY}"/ecosadmin.tcl list
if this works, then
tclsh "${ECOS_REPOSITORY}"/ecosadmin.tcl add foo.epk
Sergei
> Thanks for advice and best regards - Bob
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-03-08 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 11:06 Bob Brusa
2013-03-08 12:41 ` Sergei Gavrikov [this message]
2013-03-08 14:39 ` Bob Brusa
2013-03-08 18:56 ` Sergei Gavrikov
2013-03-09 9:14 ` [ECOS] " John Dallaway
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=alpine.DEB.2.00.1303081535180.2542@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--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).