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
36 lines
1.3 KiB
TOML
36 lines
1.3 KiB
TOML
[package]
|
|
name = "wiggle"
|
|
version = "0.14.0"
|
|
authors = ["Pat Hickey <phickey@fastly.com>", "Jakub Konka <kubkonk@jakubkonka.com>", "Alex Crichton <alex@alexcrichton.com>"]
|
|
edition = "2018"
|
|
license = "Apache-2.0 WITH LLVM-exception"
|
|
description = "Runtime components of wiggle code generator"
|
|
categories = ["wasm"]
|
|
keywords = ["webassembly", "wasm"]
|
|
repository = "https://github.com/bytecodealliance/wasmtime"
|
|
include = ["src/**/*", "LICENSE"]
|
|
|
|
[dependencies]
|
|
thiserror = "1"
|
|
witx = { path = "../wasi-common/WASI/tools/witx", version = "0.8.4", optional = true }
|
|
wiggle-macro = { path = "macro", version = "0.14.0" }
|
|
|
|
[badges]
|
|
maintenance = { status = "actively-developed" }
|
|
|
|
[dev-dependencies]
|
|
wiggle-test = { path = "test-helpers", version = "0.14.0" }
|
|
proptest = "0.9"
|
|
|
|
[features]
|
|
# These features have no effect on the users of this crate. They are only
|
|
# necessary for testing.
|
|
# The wiggle proc-macro emits some code (inside `pub mod metadata`) guarded
|
|
# by the `wiggle_metadata` feature flag. We use this feature flag so that
|
|
# users of wiggle are not forced to take a direct dependency on the `witx`
|
|
# crate unless they want it.
|
|
wiggle_metadata = ['witx', "wiggle-macro/wiggle_metadata"]
|
|
# In order to test that the contents of this metadata module meet
|
|
# expectations, we must have this feature enabled for the crate by default.
|
|
default = ["wiggle_metadata"]
|