dep: Optionalize wasm-opt
crate dependency
#63
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
wasm-opt
crate brings in C++ dependencies (binaryen) and it makes the build process more complex and slower (also setting up cross-compilation for C++ is not trivial unlike Rust). Also the DCE process doesn't make much difference if we allow all WASI subsystems.This commit makes the
wasm-opt
crate dependency optional so that crate users can choose whether to use it or not.Also strip the "name" section at walrus module generation time if
debug=false
because it was stripped bywasm-opt
before.Data point
We use wasi-virt to embed Ruby installation package with
--allow-all
:At least for us, more 300 bytes to simplify build is fine.