Skip to content

Commit 3038e4f

Browse files
committed
Rename wasm32-wasi to wasm32-wasi-preview1
1 parent a4a1a7c commit 3038e4f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/building/how-to-build-and-run.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -218,10 +218,10 @@ want to build this component:
218218
To produce a compiler that can cross-compile for other targets,
219219
pass any number of `target` flags to `x.py build`.
220220
For example, if your host platform is `x86_64-unknown-linux-gnu`
221-
and your cross-compilation target is `wasm32-wasi`, you can build with:
221+
and your cross-compilation target is `wasm32-wasi-preview1`, you can build with:
222222

223223
```bash
224-
./x.py build --target x86_64-unknown-linux-gnu --target wasm32-wasi
224+
./x.py build --target x86_64-unknown-linux-gnu --target wasm32-wasi-preview1
225225
```
226226

227227
Note that if you want the resulting compiler to be able to build crates that
@@ -233,7 +233,7 @@ you can configure this in the `[build]` section of your `config.toml` like so:
233233

234234
```toml
235235
[build]
236-
target = ["x86_64-unknown-linux-gnu", "wasm32-wasi"]
236+
target = ["x86_64-unknown-linux-gnu", "wasm32-wasi-preview1"]
237237
```
238238

239239
Note that building for some targets requires having external dependencies installed
@@ -254,7 +254,7 @@ If you have followed the directions from the prior section on creating a rustup
254254
then once you have built your compiler you will be able to use it to cross-compile like so:
255255

256256
```bash
257-
cargo +stage1 build --target wasm32-wasi
257+
cargo +stage1 build --target wasm32-wasi-preview1
258258
```
259259

260260
## Other `x.py` commands

0 commit comments

Comments
 (0)