This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: toolchain etc... for cvs.
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Dariush Pietrzak <eyck at forumakad dot pl>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 01 Feb 2005 10:45:57 -0700
- Subject: Re: [ECOS] toolchain etc... for cvs.
- Organization: MLB Associates
- References: <20050201173451.GA23858@forumakad.pl>
On Tue, 2005-02-01 at 18:34 +0100, Dariush Pietrzak wrote:
> Hi,
> is eCos designed to work with certain toolchain - ie
> if I would like to use cvs, should I use toolchains created by tcl-install,
> created by method ( and components versions ) described in
> http://ecos.sourceware.org/build-toolchain.html, or can/should I upgrade
> some of those?
>
> Ideally I would like to use crosstool, which is very reliable and I have
> been very happy with in the past, but it uses glib instead of newlib.
You can happily use your installed tools with the CVS sources - there
should be no need to update.
eCos does not use newlib - it's only part of the build process to make
GCC happy. Also, I doubt that crosstool has been set up to build the
embedded tools (e.g. arm-elf) that eCos uses.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss