[EMAIL PROTECTED] wrote:
>
> It's been awhile since I've been able to muck around with XPCOM
> standalone. The last two months, every time I've tried to get a good
> Win32 build of XPCOM standalone I've failed miserably.
>
> What's the status on XPCOM standalone support? Has this fallen off the
> map?
>
> I could go back to an earlier version (which I will probably do now
> that I'm feeling the need to be using XPCOM in my project again),
> however, the reason I keep trying newer versions is that I also use
> SpiderMonkey and would like to get XPCOM and JavaScript communicating
> in my app without the overhead of ALL of Mozilla included (and even
> then, some of the stuff I'm doing is almost certainly NOT compatible
> with Mozilla). The last few times I've grabbed XPCOM Standalone, it's
> built SpiderMonkey fine (to my surprise, before SpiderMonkey was
> completely seperate)! I just haven't gotten a good XPCOM build since
> Nov or so.
>
> Is XPCOM Standalone better supported on linux?
>
> FYI: I want to write an XPCOM object that implements some OpenGL based
> interfaces I can expose to JavaScript.
>
> Sent via Deja.com
> http://www.deja.com/
What problem are you seeing? I pull and build
xpconnect_standalone now and then. xpconnect_standalone is a
superset or xpcom_standalone - and apparently what you want. I've
seen it occasionally be broken and I get it fixed as soon as I
notice. Others do the same.
There are not a lot of people using this variant. There is no
automation to ensure that it keeps working or inform people when
they break it. Just us chickens.
Again, please say what you see breaking. Also, note that rebuild
dependency stuff is not automatic on the Windows build. So you
either need to do a clobber or do a depend build in the correct
directories before you rebuild. [I'm playing with adding a
depend_xpconnect target to client.mak now.]
John.
