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

Generate trace logs in wiggle albeit behind a feature gate

2020-03-30 19:58:15 +02:00

Cargo.toml

Move back to only one WASI submodule (#1434 )

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

LICENSE

Shuffle around the wiggle crates (#1414 )

2020-03-26 18:34:50 -05:00

README.md

Shuffle around the wiggle crates (#1414 )

2020-03-26 18:34:50 -05:00

README.md

wiggle-generate

This is a library crate that implements all of the component parts of the wiggle proc-macro crate.

Code lives in a separate non-proc-macro crate so that it can be reused in other settings, e.g. the lucet-wiggle crate.

Code generated by this crate should not have any references to a particular WebAssembly runtime or engine. It should instead expose traits that may be implemented by an engine. Today, it is consumed by both Lucet and Wasmtime.