"wasm32-unknown-wasi" is now "wasm32-wasi".
This commit is contained in:
@@ -29,14 +29,14 @@ toolchains will be able to implement WASI as well!
|
||||
To install a WASI-enabled Rust toolchain:
|
||||
|
||||
```
|
||||
rustup target add wasm32-unknown-wasi --toolchain nightly
|
||||
cargo +nightly build --target wasm32-unknown-wasi
|
||||
rustup target add wasm32-wasi --toolchain nightly
|
||||
cargo +nightly build --target wasm32-wasi
|
||||
```
|
||||
|
||||
Until now, Rust's WebAssembly support has had two main options, the
|
||||
Emscripten-based option, and the wasm32-unknown-unknown option. The latter
|
||||
option is lighter-weight, but only supports `no_std`. WASI enables a new
|
||||
wasm32-unknown-wasi target, which is similar to wasm32-unknown-unknown in
|
||||
wasm32-wasi target, which is similar to wasm32-unknown-unknown in
|
||||
that it doesn't depend on Emscripten, but it can use WASI to provide a
|
||||
decent subset of libstd.
|
||||
|
||||
|
||||
@@ -145,14 +145,14 @@ Let's put this source in the main file of our crate `src/main.rs`.
|
||||
In order to build it, we first need to install a WASI-enabled Rust toolchain:
|
||||
|
||||
```
|
||||
$ rustup target add wasm32-unknown-wasi --toolchain nightly
|
||||
$ cargo +nightly build --target wasm32-unknown-wasi
|
||||
$ rustup target add wasm32-wasi --toolchain nightly
|
||||
$ cargo +nightly build --target wasm32-wasi
|
||||
```
|
||||
|
||||
We should now have the WebAssembly module created in `target/wasm32-unknown-wasi/debug`:
|
||||
We should now have the WebAssembly module created in `target/wasm32-wasi/debug`:
|
||||
|
||||
```
|
||||
$ file target/wasm32-unknown-wasi/debug/demo.wasm
|
||||
$ file target/wasm32-wasi/debug/demo.wasm
|
||||
demo.wasm: WebAssembly (wasm) binary module version 0x1 (MVP)
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user