Hi,
I'm a newbie with XPCOM. I'm developting a XPCOM binding for Erlang, so I will have a lot of questions for this list :)
The firsts ones are about the mozilla source code and component compiling:
I want to isolate my code from the mozilla source, defining some paths that pointto mozilla and xpcom headers and libraries in a Makefile, so the user only needs the headers and the compiled library (libxpcom.so). I don't want to deploy my code into the mozilla source tree, like plXPCOM or PyXPCOM do.
Actually, to build a XPCOM binding (that uses the XPCOM internals like InterfaceInfoManager), I need a lot of c++ headers from public xpidl (p.e. mozilla/xpcom/reflect/xptinfo/public/nsIInterfaceInfoManager.idl), that are not included in the Gecko SDK, so I have to configure and compile ALL the mozilla source code (and, consequently GLib, GTK, libIDL, etc, etc, etc...).
Is there any way to get just the headers that I need? Something like an Extended Gecko SDK.
Thank you very much. --
Saudos H�ctor
_______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
