[ECOS] RE: You need ecosconfig and a toolchain

[ECOS] RE: You need ecosconfig and a toolchain

[Eric Castle]

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

Re: [ECOS] RE: You need ecosconfig and a toolchain

[Andrew Lunn]

On Tue, May 25, 2004 at 04:52:38PM -0400, Eric Castle wrote:
> 
> 
> 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? 

Those tools should work fine.

        Andrew

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

Re: [ECOS] RE: You need ecosconfig and a toolchain

[Bart Veer]

>>>>> "Eric" == Eric Castle <ecastle@umich.edu> writes:


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

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

These should all still work fine with anoncvs.

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

The toplevel configure script looks for host-side sources in two
places. First it looks for a toplevel host subdirectory. Then it
searches for package-specific host-side support, i.e. host
subdirectories within each package.

The toplevel host subdirectory is a separate CVS module so it will not
automatically be present in an anoncvs tree. If you really need it
then you will have to do a cvs checkout of the ecos-host module. Most
people just use the existing binaries.

A number of packages have their own host-side support, e.g. for the
Linux synthetic target. I believe that, at present, if you are
configuring on a cygwin host then there is nothing to build for any of
these packages. Hence the make is a no-op.

Bart

-- 
Bart Veer                       eCos Configuration Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts

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

RE: [ECOS] RE: You need ecosconfig and a toolchain

[Eric Castle]

So, basically, there's nothing we need to build here?  (We don't need to run
the "configure" script, nor make, make install?)

-----Original Message-----
From: Bart Veer [mailto:bartv@ecoscentric.com] 
Sent: Tuesday, May 25, 2004 4:07 PM
To: ecastle@umich.edu
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RE: You need ecosconfig and a toolchain

>>>>> "Eric" == Eric Castle <ecastle@umich.edu> writes:


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

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

These should all still work fine with anoncvs.

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

The toplevel configure script looks for host-side sources in two
places. First it looks for a toplevel host subdirectory. Then it
searches for package-specific host-side support, i.e. host
subdirectories within each package.

The toplevel host subdirectory is a separate CVS module so it will not
automatically be present in an anoncvs tree. If you really need it
then you will have to do a cvs checkout of the ecos-host module. Most
people just use the existing binaries.

A number of packages have their own host-side support, e.g. for the
Linux synthetic target. I believe that, at present, if you are
configuring on a cygwin host then there is nothing to build for any of
these packages. Hence the make is a no-op.

Bart

-- 
Bart Veer                       eCos Configuration Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts



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