Subj : Re: JS_DestroyContext() access violation.. To : netscape.public.mozilla.jseng From : njaguar Date : Fri Feb 28 2003 10:08 pm On Fri, 28 Feb 2003 09:15:30 -0800, Brendan Eich wrote: >> >> >>Again, I can't get the darned thing to compile! I put all the nspr >>stuff in the js src dir, add JS_THREADSAFE as a define, and it throws >>out tons of mac defines not found errors.. so either I gotta delete >>HUGE (and many) chunks of code to get it to compile (which I don't >>really want to deal with), or I gotta somehow find where those files >>are... They weren't included with the spidermonkey release, nor with >>the nspr release.. :( >> > >What are these header files? Name three, for example. I asked Phil >Schwartau to see if RC5 lacked any files that >were in RC4a. What platform and compiler are you building on? > >/be Okay, I finally got it to compile.. I was accidentally trying to use the nspr source, rather than a OS specific pre-compiled file with all the headers and libs... However, now I get strange results.. Compiling with Maximize Speed produces dozens of 1001 INTERNAL COMPILER ERRORs... Compiling with Minimize Size causes the dll to NOT work with my current compiled application (dll), it gives tons of script mistakes where there are none. A simple function that outputs the parameter of the function says the parameter is undefined! So, turning off all optimizations makes scripts "work" .. Except two problems, one, the dll size is almost twice the optimized size, and two, whenever I detach my DLL it crashes the parent application... Not sure what the problem(s) might be, but this is kind of disconcerting that newer versions would be completely incompatable with my already compiled code... (Kinda of enlightening at the same time as to why some people just _cant_ get it to work, they probably were using a different version of the dll..) Thanks in advance, I'd really like to use the latest js32 build (with JS_THREADSAFE enabled).. --Paul .