[ECOS] eCos 3.0 and newlib in ARM toolchain

[ECOS] eCos 3.0 and newlib in ARM toolchain

[Marcos Del Puerto]

Hi everybody,

I have been checking the ecos pre-built toolchain for ARM kindly
contributed by ecoscentric
(ecoscentric-gnutools-arm-eabi-20081213-sw.cygwin.tar.bz2) to use it
with eCos 3.0 and I have realized there is no newlib.h file anymore.
In fact the only reference to newlib I could found was --with-newlib
in the arm-eabi\bin\arm-eabi-gccbug file (and a couple or headers
which begin with "// Specific definitions for newlib  -*- C++ -*-").

Previous arm toolchain
(ecoscentric-gnutools-arm-elf-1.4-2.cygwin.tar.bz2) contained newlib
1.11.0 and all the respective headers. The latest EABI/ARM toolchain
provided by CodeSourcery also contains those files and newlib 1.16.0.

Does it means newlib has been dropped from the recommended toolchain?
Does it means that if I want to use newlib I will have to assemble and
compile my own toolset? Which are the advantages of using glibc for
embedded development when not using Linux?

Thank you in advance,
Marcos Del Puerto

-- 
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] eCos 3.0 and newlib in ARM toolchain

[Andrew Lunn]

> Does it means newlib has been dropped from the recommended toolchain?
> Does it means that if I want to use newlib I will have to assemble and
> compile my own toolset? Which are the advantages of using glibc for
> embedded development when not using Linux?

newlib was never used by eCos. It was only used to build the
toolchain. 

eCos has its own libc, which is not newlib and is not glibc. The eCos
libc is smaller than newlib and glibc, making it more suitable for
deeply embedded systems.

       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] eCos 3.0 and newlib in ARM toolchain

[Marcos Del Puerto]

Thank you very much for your quick answer

On Mon, May 11, 2009 at 5:43 PM, Andrew Lunn <andrew@lunn.ch> wrote:
>> Does it means newlib has been dropped from the recommended toolchain?
>> Does it means that if I want to use newlib I will have to assemble and
>> compile my own toolset? Which are the advantages of using glibc for
>> embedded development when not using Linux?
>
> newlib was never used by eCos. It was only used to build the
> toolchain.
>
> eCos has its own libc, which is not newlib and is not glibc. The eCos
> libc is smaller than newlib and glibc, making it more suitable for
> deeply embedded systems.
>
>       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