Axel Hecht wrote:
xpcom can be used standalone. Transformiix does that, for example. You might see http://bugzilla.mozilla.org/show_bug.cgi?id=183321, too.
I wonder if anybody is going to fix up xpconnect standalone, that would probably need that same hand-woven love that we need for transformiix inside build/unix/modules.mk
Thanks for the update.
Assuming xpconnect standalone is broken for the moment, what do we need to build our own xpcom components and control them via js? Using the 1.1 build is not an option since we don't want to be stuck using something that's more or less unsupported.
One good thing would be to focus on GRE. Depends on your situation, but if your client may have already an installation of a, say, Mozilla1.4, just use that instead of shipping the system again. That's the whole point of the GRE. Docs are linked from the embedding pages.
What happened that broke xpconnect standalone?
Lack of attention, to be blunt. You should have compiled xpconnect once a month and filed bugs, maybe even fixed them. Sad story, but true.
Uli
