On Sun, Sep 12, 2004 at 09:30:53PM +0200, Jens Thiele wrote:
I guess the default compilation configuration includes some stuff not really required and it is possible to reduce the size (especially of libxpcom) ?
Yes, you can disable some unused stuff, try: --disable-jsloader (unless you want to write components using javascript?)
Isn't really part of the xpcom lib.
--disable-static-component-loader I'm not quite sure what this does, but I don't think normal builds need it
This is the component loader that knows how to load components that were linked all together into what we call a "static build". It isn't needed unless you are building a "static build"
With the above options, I get:
du -Lsh libpl* libnspr4.so libxpcom.so nsTestSample
16K libplc4.so 12K libplds4.so 200K libnspr4.so 797K libxpcom.so 20K nsTestSample
Looks like ~1 MB.
(Tested with "gcc version 3.3.3 (SuSE Linux)", CVS Trunk as of yesterday)
The real question is what you want libxpcom to do? if you want it to support the mozilla applications, then we are pretty close to 800k. if you just want it to do COM w/o reflection, you can trim a huge amount out of it.
However, xpcom provides quite a bit of functionality and wrappers of lower level services: file abstraction, threading, many data structures, etc.
DougT
_______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
