* 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
26 lines
728 B
TOML
26 lines
728 B
TOML
[package]
|
|
name = "wiggle-macro"
|
|
version = "0.14.0"
|
|
authors = ["Pat Hickey <phickey@fastly.com>", "Jakub Konka <kubkon@jakubkonka.com>", "Alex Crichton <alex@alexcrichton.com>"]
|
|
edition = "2018"
|
|
license = "Apache-2.0 WITH LLVM-exception"
|
|
description = "Wiggle code generator"
|
|
categories = ["wasm"]
|
|
keywords = ["webassembly", "wasm"]
|
|
repository = "https://github.com/bytecodealliance/wasmtime"
|
|
include = ["src/**/*", "LICENSE"]
|
|
|
|
[lib]
|
|
proc-macro = true
|
|
|
|
[dependencies]
|
|
wiggle-generate = { path = "../generate", version = "0.14.0" }
|
|
witx = { path = "../../wasi-common/WASI/tools/witx", version = "0.8.4" }
|
|
syn = { version = "1.0", features = ["full"] }
|
|
|
|
[dev-dependencies]
|
|
wiggle = { path = ".." }
|
|
|
|
[features]
|
|
wiggle_metadata = []
|