a7fbf22348
Backed out changeset e71da1f3c048 Backed out changeset 971159738904 (bug 1366287) Backed out changeset 68fae6784ebe (bug 1366287) Backed out changeset a18120245eb7 (bug 1366287) Backed out changeset 3bbd03d726e5 (bug 1366287) Backed out changeset f80aac2c702a (bug 1366287) Backed out changeset c834c0c12a7f (bug 1366287) Backed out changeset dd19d38a2b1c (bug 1366287) Backed out changeset 76fdbe405fbd (bug 1366287) Backed out changeset b424782cd5d1 (bug 1366287) Backed out changeset e4fd5393d398 (bug 1457560) |
||
|---|---|---|
| .. | ||
| etc | ||
| src | ||
| tests | ||
| .gitignore | ||
| CMakeLists.txt | ||
| Cargo.toml | ||
| README.md | ||
| build.rs | ||
README.md
The js Crate: Rust Bindings to SpiderMonkey
Building
To build a release version of SpiderMonkey and the Rust code with optimizations enabled:
$ cargo build --release
To build with SpiderMonkey's DEBUG checks and assertions:
$ cargo build --features debugmozjs
Raw FFI bindings to JSAPI are machine generated with
rust-lang-nursery/rust-bindgen, and requires libclang >= 3.9. See
./build.rs for details.
Cargo Features
-
debugmozjs: Create a DEBUG build of SpiderMonkey with many extra assertions enabled. This is decoupled from whether the crate and its Rust code is built in debug or release mode. -
promises: Enable SpiderMonkey native promises. -
nonzero: Leverage the unstableNonZerotype. Requires nightly Rust.
Testing
Make sure to test both with and without the debugmozjs feature because various
structures have different sizes and get passed through functions differently at
the ABI level! At minimum, you should test with debugmozjs to get extra
assertions and checking.
$ cargo test
$ cargo test --features debugmozjs