uClibc++ version 0.1.12 released
Garrett Kajmowicz
gkajmowi at tbaytel.net
Sun Dec 11 15:29:31 UTC 2005
> I don't see a good reason to split it, the lib is small enough already, My
> tests show that the apps won't get much smaller by the small lib as in
> case of uClibc (an "incorrect" comparison: firefox 41 MB glibc+libstdc++,
> 39 MB uClibc+uClibc++) and there are not so many small C++ apps around,
> rather bigger projects where the size of this lib won't matter
>
The purpose of splitting the library is not to make things smaller - in fact,
with the overhead of multiple ELF headers, the combined total will get
bigger. Rob's idea was that by splitting out these components, it might be
easier to sucker^H^H^H^H^H^H attract some body/person into writting the
compiler integration component (ie replace the wrapper with a compiler
modification).
I'm still not convinced that this is the best approach, but I wanted to
clarify the reasoning.
- Garrett
More information about the uClibc
mailing list