Subj : Re: Building thread-safe SpiderMonkey for Win32
To   : netscape.public.mozilla.jseng
From : Bob Kline <bkline@rksystems.com>
Date : Wed Mar 17 2004 11:58 am

Brendan Eich wrote:

> Bob Kline wrote:
> 
>> I'm working on providing the Sablotron (open-source XSL/T package) as 
>> much information as I can on making the Sablotron use of SpiderMonkey 
>> thread-safe, and I have a question about the WIN32 makefile (js.mak) 
>> shipped with the js-1.5-rc6.tar.gz tarball.  Is there a less fragile 
>> way to maintain an environment which keeps up-to-date thread-safe 
>> builds of js32.lib/dll than to hand-edit each new version's js.mak to 
>> inject the definition for JS_THREADSAFE instructions to link in the 
>> NSPR library?
>>
> 
> If there is, I'm all for incorporating this into the standalone 
> releases.  I'm not a Windows hacker, so I can't help.  We've relied on 
> the kindness of strangers here in the past, and will again, I'm sure.
> 
> Nmake files seem old school -- is there some new VS.NET way to go, that 
> we could offer in addition?  How about Makefile.in/autoconf builds for 
> Windows, using cygwin?
> 

There actually is support for using gmake on Windows under cygwin.  It's 
just broken by a disconnect between the SpiderMonkey and NSPR 
assumptions about where the NSPR components can be found.  See my last 
two responses to Benjamin Smedberg in this ng thread.  Can a thread-safe 
SpiderMonkey be built without NSPR?

Cheers,
Bob

.