840f785b1e
Backed out changeset b2d18ea619ec (bug 1475228) Backed out changeset 45d3ffe3308e (bug 1475228) Backed out changeset 02b27f8441be (bug 1475228) Backed out changeset b82c2cf4b3f1 (bug 1475228) Backed out changeset 2bc8f24dc3fc (bug 1475228) Backed out changeset 6104ea971587 (bug 1475228) Backed out changeset 7c83633262db (bug 1475228) Backed out changeset 34fb24d52f08 (bug 1475228) |
||
|---|---|---|
| .. | ||
| 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