From: Ilija Kocho <ilijak@siva.com.mk>
To: John Dallaway <john@dallaway.org.uk>
Cc: Michael Jones <mjones@linear.com>,
eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: Installing source after full build
Date: Tue, 04 Dec 2012 16:42:00 -0000 [thread overview]
Message-ID: <50BE27FF.4020501@siva.com.mk> (raw)
In-Reply-To: <50BB197D.90400@dallaway.org.uk>
John
If there is a wish list, I think it would be a good idea to have an
option [in configtool/ecosconfig] to copy the sources into the /build/ tree.
Production of private [to the project] eCos instant would be of help for
some applications [that need certification, etc].
Ilija
On 02.12.2012 10:03, John Dallaway wrote:
> Mike
>
> On 01/12/12 20:24, Michael Jones wrote:
>
>> I could be wrong, but my observation was the ecos.db was not copied from
>> the build (meaning the ecos and ecos config tool build), and neither was
>> packages. The eCos Configuration tool certainly needs ecos.db, but I
>> assume it needs the package tree. So unless there is some environment
>> variable telling the Configuration tool where to find this, how would
>> copying only the library work?
>>
>> Perhaps you interpreted my build as the build done within the config tool.
> Yes, that is where the eCos run-time code is built.
>
>> I am talking about the build of ecos and the config tool.
> Only the host tools are built via the configure/make process.
>
> You should point the eCos Confiiguration Tool at your eCos repository
> (using the Build->Repository menu item) to configure and build the eCos
> run-time code. You should specify the directory _containing_ the eCos
> "packages" directory (not the "packages" directory itself).
>
>> I am compiling
>> the whole thing rather than using a binary distribution so that I have
>> access to the new Kinetis support.
> You should be able to use the latest Linux-hosted configtool snapshot
> build (2011-02-09) on 64-bit distros if you install the relevant 32-bit
> compatibility libraries. Ref:
>
> http://ecos.sourceware.org/ml/ecos-discuss/2011-02/msg00031.html
>
> I hope this helps...
>
> 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:[~2012-12-04 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 23:23 [ECOS] " Michael Jones
2012-12-01 18:30 ` [ECOS] " John Dallaway
2012-12-01 20:25 ` [ECOS] " Michael Jones
2012-12-02 9:04 ` [ECOS] " John Dallaway
2012-12-04 16:42 ` Ilija Kocho [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=50BE27FF.4020501@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=mjones@linear.com \
/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).