968cd76163
* 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
14 lines
551 B
Rust
14 lines
551 B
Rust
use wasi_common::old::snapshot_0::hostcalls;
|
|
pub use wasi_common::old::snapshot_0::{WasiCtx, WasiCtxBuilder};
|
|
|
|
// Defines a `struct Wasi` with member fields and appropriate APIs for dealing
|
|
// with all the various WASI exports.
|
|
wig::define_wasi_struct!("phases/old/snapshot_0/witx/wasi_unstable.witx");
|
|
|
|
pub fn is_wasi_module(name: &str) -> bool {
|
|
// FIXME: this should be more conservative, but while WASI is in flux and
|
|
// we're figuring out how to support multiple revisions, this should do the
|
|
// trick.
|
|
name.starts_with("wasi")
|
|
}
|