File tree Expand file tree Collapse file tree 2 files changed +17
-5
lines changed Expand file tree Collapse file tree 2 files changed +17
-5
lines changed Original file line number Diff line number Diff line change 1
1
[package ]
2
- name = " wasi-core "
3
- version = " 0.2 .0"
2
+ name = " wasi"
3
+ version = " 0.3 .0"
4
4
authors = [" The Cranelift Project Developers" ]
5
5
license = " Apache-2.0 WITH LLVM-exception"
6
6
description = " Experimental WASI API bindings for Rust"
7
7
edition = " 2018"
8
8
categories = [" no-std" , " wasm" ]
9
9
keywords = [" webassembly" , " wasm" ]
10
- repository = " https://github.com/CraneStation/wasi-core "
10
+ repository = " https://github.com/CraneStation/rust-wasi "
11
11
readme = " README.md"
12
- documentation = " https://docs.rs/wasi-core "
12
+ documentation = " https://docs.rs/wasi"
13
13
14
14
[dependencies ]
15
15
Original file line number Diff line number Diff line change 1
- # wasi-core
1
+ # WASI API Bindings for Rust
2
2
3
3
This package contains experimental [ WASI] ( https://github.com/WebAssembly/WASI )
4
4
API bindings in Rust.
@@ -10,3 +10,15 @@ There are two modules:
10
10
11
11
- ` wasi_unstable ` , which provides thin wrappers around the raw functions
12
12
which use idiomatic Rust types rather than raw pointers, and are safe.
13
+
14
+ This crate is quite low-level and provides conceptually a "system call"
15
+ interface. In most settings, it's better to use the Rust standard library,
16
+ which has WASI support.
17
+
18
+ To compile Rust projects to wasm using WASI, use the ` wasm32-wasi ` target,
19
+ like this:
20
+
21
+ ```
22
+ rustup target add wasm32-wasi
23
+ cargo build --target wasm32-wasi
24
+ ```
You can’t perform that action at this time.
0 commit comments