Re: [avr-gcc-list] the dynamic shared library in avr-gcc

[Joerg Wunsch]

Eric Weddington <address@hidden> wrote:

> Using shared libraries do not make sense in building an AVR
> application because there are no such concepts in an AVR code image
> as a filesystem, or multiple applications that need to share a
> library in the first place.

Also, shared libraries are typically loaded into RAM, and executed
there.  That's not possible in AVR's Harvard architecture.  While it's
in theory possible to burn the "shared library" into a (flash) ROM
segment at run-time, this is 1) a rather expensive operation (compared
to the classical shared library approach), and 2) can only be done
from inside the bootloader area for many AVRs.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)