rvolosatovs edited PR #6486:
Refs #6390
I used https://github.com/bytecodealliance/wit-deps to populate the
wit/deps
directories, I checked in the correspondingdeps.toml
anddeps.lock
files for futurewit-deps update
usage, but I did not add a dependency on the tool (yet?) by eitherbuild.rs
integration or direct binary usage like was requested in https://github.com/bytecodealliance/preview2-prototyping/pull/136 earlierI also did not touch
crates/wasi/wit/deps
other thanpreview
, since package is using dependency versions, which are different from upstream
- update outdated WIT files
- move
crates/wasi/wit/deps/preview
tocrates/wasi/wit
, sincepreview
package is the WASI package- fix
cargo vendor
use cases (downstream crates utilizing Wasmtime viacargo vendor
) by ensuring that all WIT-using crates are self-contained- use consistent naming and location scheme for dependencies (e.g.
deps/cli-base
forwasi:cli-base
, just likedeps/io
is used forwasi:io
)
Last updated: Dec 23 2024 at 13:07 UTC