This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Linking problem when removing ISO C standard input/output functions
- From: Ross Younger <ecos at impropriety dot org dot uk>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 07 Sep 2011 19:30:00 +1200
- Subject: Re: [ECOS] Linking problem when removing ISO C standard input/output functions
- References: <20110906213341.14310@gmx.net>
On 07/09/11 09:33, Alois Z. wrote:
I have a very strange problem. I'm currently removing not needed features from my eCos configuration in order to save some space for a rather small system.
Generally, removing features from your eCos configuration doesn't save
you anything in your built image. eCos was specifically designed to make
good use of link-time garbage collection; that is to say, if your
application doesn't use a facility provided by the OS, the code for that
facility does not appear in the final linked image. So to achieve a
smaller footprint, you have to make your application use less of the OS.
An alternative strategy for you might be to start with the `minimal'
eCos template and build up your configuation from there based on what
your application actually needs. This may not save you very much, for
the reasons described above.
Ross
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss