mirrors/litbwraw
1
0
Fork 0
mirror of https://github.com/bytedream/litbwraw.git synced 2025-05-09 04:05:12 +02:00
Code Issues Packages Projects Releases Wiki Activity

update testing compile issue notice

Browse Source
This commit is contained in:
bytedream 2024-01-16 18:27:03 +01:00
parent 06433feedf
commit 8c6ef99206
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/testing.md
View File

@ -8,8 +8,8 @@ You have to specify the test runner which executes the Javascript, either in the
If your crate is a library, you also have to remove the `-o<library name>.js` compiler option as it modifies the output filename which the Rust test suite can't track.
Because the `test` subcommand compiles the tests as normal binaries, the Emscripten compiler automatically creates the js glue.
> Also, in the current stable Rust, you have to set the `-sERROR_ON_UNDEFINED_SYMBOLS=0` compiler option in order to avoid test compilation errors. This is due to an incompatibility between emscripten and the internal Rust libc crate ([rust-lang/rust#116655](https://github.com/rust-lang/rust/issues/116655)) but a fix for it should land in Rust 1.75 ([rust-lang/rust#116527](https://github.com/rust-lang/rust/pull/116527)).
> Alternatively you can use the nightly toolchain, the fix is already present there.
> Before Rust 1.75 there were a major incompatibility between emscripten and the internal Rust libc crate ([rust-lang/rust#116655](https://github.com/rust-lang/rust/issues/116655)) which always resulted in a compiler error.
> To prevent this issue, you have to set the `-sERROR_ON_UNDEFINED_SYMBOLS=0` compiler option.
With this done, we can create a simple test:
```rust,ignore