[ECOS] RE: You need ecosconfig and a toolchain

["Eric Castle" <ecastle at umich dot edu>]

Bill,

As for the cross toolchain, we're currently using the precompiled one for
powerpc (the 2.0 release).  This is also how we got a copy of ecosconfig.

Will these tools work with the CVS version?  Or do we need to follow the
instructions listed at http://ecos.sourceware.org/build-toolchain.html to
get an updated tool chain?

The rest of what we were doing was trying to follow the instructions listed
in the README.host that's included in the CVS files.  It appears to be for
building updated versions of ecosconfig and other important things.  I got
the impression that I should be running this configure script, followed by
make, and make install.  This is the part where, nothing seems to happen
when we run "make."  It goes into a bunch of directories, but never actually
builds anything anywhere.

We've been trying to use ecosconfig like you said, but we've been having
difficulty with an iram error (see my coworker's post today for that).

  

-----Original Message-----
From: Bill Siegmund [mailto:billsiegmund@cruzio.com] 
Sent: Tuesday, May 25, 2004 11:12 AM
To: ecastle@umich.edu
Subject: You need ecosconfig and a toolchain

Eric,
    You got the first two steps right.
1. Downloaded the CVS eCos stuff into a folder called cvs-ecos per the
instructions on the webpage.
2. Set the path according to the instructions on the webpage for the eCos
repository.
    But you need to build a cross toolchain for your host and target
unless you can download it from the eCosCentric site or install it
from their $50 CD. See the instructions at
http://ecos.sourceware.org/build-toolchain.html

    And you need to get a copy of ecosconfig.
Or build it from the source in
CVS*/ecos/host/bld/tools/configtool/standalone/common
using the Makefile there.

    Your third step is likely to cause clutter and confusion.
3. Made a "build" directory within cvs-ecos, switched into there.
And it isn't necessary. I do my builds in a "projects" directory on
a different drive.

    Your fourth step is wrong. As far as I can recall,
I've never had to do this.
4. Ran configure as follows:
	../ecos/configure --prefix=/usr/local/ecos --enable-debug

    What you should be doing in a "projects" directory
after getting a copy of ecosconfig in a directory in your path is

ecosconfig new <target> <build type>
ecosconfig tree
make
make tests

    You can find the current targets
by searching your "ecos.db" for "target"

    The build types that come to mind are
minimal
default
kernel
net
posix
all

Bill Siegmund
Boulder Creek, California






-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss