On 10/24/13 5:53 PM, Nicholas Nethercote wrote: > On Thu, Oct 24, 2013 at 5:36 PM, Jason Orendorff <jorendo...@mozilla.com> > wrote: >> Everyone please at least consider fixing up your dev environment to >> build with NSPR. > Where are the instructions? > > Nick
This is one of those rare cases where the documentation actually contains exactly the useful bits you need: https://developer.mozilla.org/en-US/docs/SpiderMonkey/Build_Documentation#Building Personally I use: --enable-threadsafe --with-nspr-cflags=-I${MY_FIREFOX_OBJDIR}/dist/include/nspr "--with-nspr-libs=-L${MY_FIREFOX_OBJDIR}/dist/lib -lnspr4" --enable-ctypes If you know want the full details, do ${SRCDIR}/configure --help. You need to understand GNU-style configury pretty well to fully grok the results, though: --with-system-nspr Use an NSPR that is already built and installed. Use the 'nspr-config' script in the current path, or look for the script in the directories given with --with-nspr-exec-prefix or --with-nspr-prefix. (Those flags are only checked if you specify --with-system-nspr.) --with-nspr-cflags=FLAGS Pass FLAGS to CC when building code that uses NSPR. Use this when there's no accurate nspr-config script available. This is the case when building SpiderMonkey as part of the Mozilla tree: the top-level configure script computes NSPR flags that accomodate the quirks of that environment. --with-nspr-libs=LIBS Pass LIBS to LD when linking code that uses NSPR. See --with-nspr-cflags for more details. --with-nspr-prefix=PFX Prefix where NSPR is installed --with-nspr-exec-prefix=PFX Exec prefix where NSPR is installed All this documentation work is due to Jim Blandy. -j _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals