Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
The bindings are to the raw SpiderMonkey API, higher-level bindings are in the rust-mozjs repository.
Install Clang (at least version 3.9) and autoconf v 2.13, for example in a Debian-based Linux:
sudo apt-get install clang-6.0 autoconf2.13
If you have more than one version of Clang installed, you can set the
environment variable, for example:
Open up a shell configured to use Visual Studio. This could be the one included with Visual Studio (e.g. Visual Studio 2017 / X64 Native Tools Command Prompt for VS 2017) or a shell in which you have run
"c:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
- Set the
MOZTOOLS_PATHenvironment variable to point to the tools from the Mozilla Build Package:
- Download and install Clang for Windows (64 bit) from https://releases.llvm.org/download.html
and set the
LIBCLANG_PATHenvironment variable to its
set LIBCLANG_PATH=C:\Program Files\LLVM\lib
- Set environment variables so the build script can find Python 2.7 and Autoconf 2.13:
set AUTOCONF=C:\mozilla-build\msys\local\bin\autoconf-2.13 set NATIVE_WIN32_PYTHON=C:\mozilla-build\python\python2.7.exe
You can now build and test the crate using cargo:
cargo build cargo test cargo build --features debugmozjs cargo test --features debugmozjs
In order to upgrade to a new version of SpiderMonkey:
Find the mozilla-release commit for the desired version of SpiderMonkey, at https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&filter-searchStr=spidermonkey%20pkg. You are looking for an SM(pkg) tagged with FIREFOX_RELEASE. Take a note of the commit number to the left (a hex number such as ac4fbb7aaca0).
Click on the SM(pkg) link, which will open a panel with details of the commit, including an artefact uploaded link, with a name of the form mozjs-version.tar.bz2. Download it and save it locally.
Look at the patches in
etc/patches/*.patch, and remove any that no longer apply (with a bit of luck this will be all of them).
python3 ./etc/update.py path/to/tarball.
etc/COMMITwith the commit number.
Build and test the bindings as above, then submit a PR!