I pull and build xpconnect standalone on windows every couple of days and it
works fine for me. There has been a change from XP_PC to using XP_WIN or
XP_OS2. You need to change this define before rebuilding your app. Without
changing this define you will end up with very hard to debug run-time
errors.
PS - I filed a bug asking that use of XP_PC generate a compiler error. But
it hasn't be acted on.
Jon Smirl
[EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote in message 955oe7$dec$[EMAIL PROTECTED]">news:955oe7$dec$[EMAIL PROTECTED]...
> 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/
