Hi, I am currently using spidermonkey as scripting engine and generate my wrappers around native C/C++ code manually (and partially by scripts). I now started to implement a module framework which allows to load native code at runtime (dlopen via. libltdl) from within javascript - and register new objects. Now I think this looks like duplicating what xpcom already does.
Now I am evaluating if xpcom would fit my needs where size is my major concern. I successfully compiled the standalone xpcom (from mozilla-firefox-0.9.3) and the nsTestSample. (everything on linux/i386) The needed files: $find ./nsTestSample ./libplds4.so ./libplc4.so ./libnspr4.so ./libxpcom.so ./components ./components/compreg.dat ./components/xpti.dat ./components/libxpcomsample.so Total size: du -sh 1,7M . where libxpcom.so is 1.4M I guess the default compilation configuration includes some stuff not really required and it is possible to reduce the size (especially of libxpcom) ? What size could I expect as minimum? Any experiences? Suggestions how to strip it down? Thanks Jens PS: How stable is the xpcom "api" _______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
