> 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. >
Thanks for pointing this out to me. I did it from the wrong side. I found the stdio stuff in my map file so I removed it from my eCos config and than eliminated the only two occurrences in my project. Now that the usage of stdio stuff is gone so the link-time garbage collection perfectly works and saved my quite a bunch of space. There is just one thing I have in my map file I would like to have gone. There are several methods on hal_diag_mangler_* and console as well as serial com stuff. As I don't have access to any com port I would also like to get rid of this stuff too. Can anybody give me a hint where to start here. Thanks, Alois -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
