T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

"wasm32-unknown-wasi" is now "wasm32-wasi".

Browse Source
This commit is contained in:
Dan Gohman
2019-05-13 21:39:39 -07:00
parent 1c0efd03b3
commit 2b5be77fa5
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/WASI-intro.md
View File

@@ -29,14 +29,14 @@ toolchains will be able to implement WASI as well!
To install a WASI-enabled Rust toolchain: To install a WASI-enabled Rust toolchain:
``` ```
rustup target add wasm32-unknown-wasi --toolchain nightly rustup target add wasm32-wasi --toolchain nightly
cargo +nightly build --target wasm32-unknown-wasi cargo +nightly build --target wasm32-wasi
``` ```
Until now, Rust's WebAssembly support has had two main options, the Until now, Rust's WebAssembly support has had two main options, the
Emscripten-based option, and the wasm32-unknown-unknown option. The latter Emscripten-based option, and the wasm32-unknown-unknown option. The latter
option is lighter-weight, but only supports `no_std`. WASI enables a new 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 that it doesn't depend on Emscripten, but it can use WASI to provide a
decent subset of libstd. decent subset of libstd.

8
docs/WASI-tutorial.md
View File

@@ -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: In order to build it, we first need to install a WASI-enabled Rust toolchain:
``` ```
$ rustup target add wasm32-unknown-wasi --toolchain nightly $ rustup target add wasm32-wasi --toolchain nightly
$ cargo +nightly build --target wasm32-unknown-wasi $ 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) demo.wasm: WebAssembly (wasm) binary module version 0x1 (MVP)
``` ```