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
16 lines
255 B
Rust
16 lines
255 B
Rust
mod ctx;
|
|
mod entry;
|
|
mod helpers;
|
|
mod host;
|
|
mod hostcalls_impl;
|
|
mod memory;
|
|
mod sys;
|
|
pub mod wasi;
|
|
pub mod wasi32;
|
|
|
|
pub mod hostcalls {
|
|
wig::define_hostcalls!("phases/old/snapshot_0/witx/wasi_unstable.witx");
|
|
}
|
|
|
|
pub use ctx::{WasiCtx, WasiCtxBuilder};
|