Files

Alex Crichton 968cd76163 Move back to only one WASI submodule (#1434 )

* Move back to only one WASI submodule

This commit fixes the issue where we have two WASI submodules for build
reasons in this repository. The fix was to place the submodule in the
`wasi-common` crate, and then anyone using the `wig` crate has to be
sure to define a `WASI_ROOT` env var in a build script to be able to
parse witx files.

With all that in place `wasi-common` becomes the source of truth for the
witx files we're parsing, and crates like `wasmtime-wasi` use
build-scripts shenanigans to read the same witx files. This should
hopefully get us so we're compatible with publishing and still only have
one submodule!

* rustfmt

2020-03-30 14:45:23 -05:00

src

Move back to only one WASI submodule (#1434 )

2020-03-30 14:45:23 -05:00

WASI @ 068b282abf

Fixes for cargo publish (#1416 )

2020-03-26 20:31:12 -07:00

wig

Move back to only one WASI submodule (#1434 )

2020-03-30 14:45:23 -05:00

winx

Test 0.14 (#1417 )

2020-03-26 21:53:42 -07:00

yanix

Test 0.14 (#1417 )

2020-03-26 21:53:42 -07:00

build.rs

Move back to only one WASI submodule (#1434 )

2020-03-30 14:45:23 -05:00

Cargo.toml

Move back to only one WASI submodule (#1434 )

2020-03-30 14:45:23 -05:00

LICENSE

Initial reorg.

2019-11-08 06:35:40 -08:00

LICENSE.cloudabi-utils

Initial reorg.

2019-11-08 06:35:40 -08:00

README.md

Fixes for cargo publish (#1416 )

2020-03-26 20:31:12 -07:00

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.

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 socket hostcalls:

sock_recv
sock_send
sock_shutdown

We expect these to be implemented when network access is standardised.

We also currently do not support 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

Third-Party Code

Significant parts of our hostcall implementations are derived from the C implementations in cloudabi-utils. See LICENSE.cloudabi-utils for license information.