This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Application build
- From: Andrew Lunn <andrew dot lunn at ascom dot ch>
- To: Lin Ming <lm1121 at yeah dot net>
- Cc: Ecos-List <ecos-discuss at sources dot redhat dot com>
- Date: Tue, 20 Aug 2002 09:24:46 +0200
- Subject: Re: [ECOS] Application build
- References: <200208200311.g7K3BbW08735@ascomax.hasler.ascom.ch>
Hi Lin.
The application includes the parts of eCos its needs, not the whole
OS. The linker is clever enough to leave out functions that are not
references.
The configuration of eCos can have some effect on code size. If you
disable a package, you know for sure its not going to get linked
in. This particularly applies to device drivers.
One thing to be aware of. The size of the elf image is very different
from the size of the binary. The elf may be huge, but once you have
turned it into a binary, it will be much smaller.
Andrew
On Tue, Aug 20, 2002 at 11:09:55AM +0800, Lin Ming wrote:
> Hi All,
>
>
> If I make a simple application, will the binary code include all the OS?
>
> Is that (I mean the included OS code size) related to the template I
> built in ecos configuration tool or the applicaiton I make?
>
> Anybody can make me clear to this? Thanks!!
>
>
>
> Best Regards,
> Lin Ming
> 2002-08-20
>
>
>
>
>
> --
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss