-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add WASI Interface to Wasmer #297
Comments
299: Support for the WASI ABI. r=xmclark a=lachlansneff part of #297 Co-authored-by: Lachlan Sneff <[email protected]> Co-authored-by: Mark McCaskey <[email protected]> Co-authored-by: bors[bot] <bors[bot]@users.noreply.github.com> Co-authored-by: Mark McCaskey <[email protected]>
We just merged #299 which adds initial (and experimental) support for WASI 🎉 We will keep iterating on the WASI integration, so keeping this issue open until is feature complete |
Wasmer's support for WASI is pretty decent already! You should ask to be listed here https://wasi.dev |
Thanks for the ping! We will need to submit PRs to the following repos:
@Hywan do you want to handle this? :) |
Related issue in Wasmer: wasmerio/wasmer#297
I've created the issue in the wasi.dev repo adding Wasmer: bytecodealliance/wasi.dev#2 Closing the issue here since Wasmer WASI support is stable and mature now. Thanks everyone for your support! |
WASI is a WebAssembly System Interface.
Here's a detailed blogpost from Mozilla about it: https://hacks.mozilla.org/2019/03/standardizing-wasi-a-webassembly-system-interface/
Wasmer should support WASI, in a similar way we support emscripten.
So binaries/libraries can be executed with wasmer easily.
Related issues
Rust is also trying to target
wasi
from rust libraries: rust-lang/rust#59464Related docs
WASI API: https://github.com/CraneStation/wasmtime-wasi/blob/wasi/docs/WASI-api.md
The text was updated successfully, but these errors were encountered: