public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
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: Sun, 02 Dec 2012 09:04:00 -0000	[thread overview]
Message-ID: <50BB197D.90400@dallaway.org.uk> (raw)
In-Reply-To: <27451076-2A19-4F5B-8D40-DAD018AB696D@linear.com>

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

  reply	other threads:[~2012-12-02  9:04 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     ` John Dallaway [this message]
2012-12-04 16:42       ` [ECOS] " 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=50BB197D.90400@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).