You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Juniper Tyree e5817d9602
Make wasmtime dependency in wiggle and wasi-common optional with a default feature (#7792)
10 months ago
..
WASI@0ba0c5e2e3 Implement `sock_accept` 3 years ago
cap-std-sync Configure workspace lints, enable running some Clippy lints on CI (#7561) 12 months ago
src fix(wasi-common): convert `ErrorKind::WouldBlock` instead of trapping (#7686) 11 months ago
tests/all Wasi test suite cleanups (#7553) 12 months ago
tokio Configure workspace lints, enable running some Clippy lints on CI (#7561) 12 months ago
Cargo.toml Make wasmtime dependency in wiggle and wasi-common optional with a default feature (#7792) 10 months ago
LICENSE Initial reorg. 5 years ago
README.md Implement the remaining socket-related WASI functions. (#4776) 2 years ago
build.rs Add "cargo:rerun-if-changed=build.rs" to some build.rs files. 3 years ago

README.md

wasi-common

A Bytecode Alliance project

A library providing a common implementation of WASI hostcalls for re-use in any WASI-enabled runtime.

Crates.io version Download docs.rs docs

The wasi-common crate will ultimately serve as a library providing a common implementation of WASI hostcalls for re-use in any WASI (and potentially non-WASI) runtimes such as Wasmtime and Lucet.

The library is an adaption of lucet-wasi crate from the Lucet project, and it is currently based on 40ae1df git revision.

Please note that the library requires Rust compiler version at least 1.37.0.

Supported syscalls

*nix

In our *nix implementation, we currently support the entire WASI API with the exception of the proc_raise hostcall, as it is expected to be dropped entirely from WASI.

Windows

In our Windows implementation, we currently support the minimal subset of WASI API which allows for running the very basic "Hello world!" style WASM apps. More coming shortly, so stay tuned!

Development hints

When testing the crate, you may want to enable and run full wasm32 integration testsuite. This requires wasm32-wasi target installed which can be done as follows using rustup

rustup target add wasm32-wasi

Now, you should be able to run the integration testsuite by running cargo test on the test-programs package with test-programs/test_programs feature enabled:

cargo test --features test-programs/test_programs --package test-programs