From: John Dallaway <john@dallaway.org.uk>
To: Michael Jones <mjones@linear.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Installing source after full build
Date: Sat, 01 Dec 2012 18:30:00 -0000 [thread overview]
Message-ID: <50BA4CA3.90307@dallaway.org.uk> (raw)
In-Reply-To: <D081CD34-4F47-4867-B8D0-81043DA23DD8@linear.com>
Mike
On 29/11/12 23:23, Michael Jones wrote:
> But I noticed that it does not copy source files or ecos.db from the
> source dir to the target dir along with the binary stuff.
>
> Is there a way to get all the code and db copied over via the make
> process or do I just have to copy it?
>
> Should I instead compile on top of the source tree directly?
When you build eCos, the eCos library (libtarget.a), linker script
(target.ld), external header files and a few miscellaneous files are
placed in the eCos "install" tree. These files are all you need to
compile application code and link it with eCos to form a self-contained
application executable. Your application code should not reference
header files located within the eCos source code repository.
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
next prev parent reply other threads:[~2012-12-01 18:30 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 ` John Dallaway [this message]
2012-12-01 20:25 ` Michael Jones
2012-12-02 9:04 ` [ECOS] " John Dallaway
2012-12-04 16:42 ` Ilija Kocho
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=50BA4CA3.90307@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@ecos.sourceware.org \
--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).