static builds versus dynamic

[Marius Groeger]

On Thu, 19 Jan 2006, Roman wrote:

> Hi,
> I am moving code to ARM 920T based board. I have compiled my code with with
> -static and without. I have played with static and with the dynamic versions
> of my code compilation. I have timed it, but I have not done any detailed
> analysis. Has anyone had the experience between the two. I wonder about the
> benefits or loss of building all support (-static) in your code. I see time
> difference on my process reports.
>
> I am curious, if anyone had experiences with static builds to share.

Static builds can save on the memory footprint (both RAM and ROM) as 
long as you have very few binaries. For instance, if your embedded 
application is only one process (replacing standard or busybox init), 
then you don't need the whole shared glibc and stuff. Depending on the 
target and application type, this flips with 2 or 3 binaries and 
you're better off with shared libraries.

Regards,
Marius

-- 
Marius Groeger <mgroeger@sysgo.com>
SYSGO AG                      Embedded and Real-Time Software
Voice: +49 6136 9948 0                  FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.pikeos.com


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org