This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Hello Code size
- To: "'Jonathan Larmour'" <jlarmour at redhat dot com>, "'Dzanh Nguyen'" <dzanh at indigita dot com>
- Subject: RE: [ECOS] Hello Code size
- From: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Date: Tue, 18 Sep 2001 14:57:29 -0600
- Cc: <ecos-discuss at sources dot redhat dot com>
Is there a guide somewhere that discusses when each package and parts of
each package are required?
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Jonathan
Larmour
Sent: Tuesday, September 18, 2001 2:51 PM
To: Dzanh Nguyen
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Hello Code size
Dzanh Nguyen wrote:
>
> I am new with the Ecos. I build the example hello.c and looked at the
map
> that the linker generated, the total code size for the hello is around
42K.
> Is Ecos footprint actually that big or I did something wrong?
eCos is a highly configurable operating system. The default
configuration
mostly tries to add functionality, rather than reduce size. You should
easily be able to reduce that footprint by orders of magnitude when you
understand the requirements of your application. For example, for hello
world, you probably wouldn't include the kernel package at all since you
aren't using multiple threads. There are various libc stdio features
like
stdio buffering that could be disabled, etc.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223)
271062
Maybe this world is another planet's Hell -Aldous Huxley ||
Opinions==mine