You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I can't figure out how to invoke xargo when using wasm-pack build. I can run xargo build --target wasm32-unknown-unknown --release, which I assume puts the output in the target directory without compiling it to the pkg directory, but then wasm-pack build just overwrites the target directory again with the non-xargo build.
The text was updated successfully, but these errors were encountered:
I think being able to use xargo instead of cargo has more general uses as well and has to be supported. For example, using wasm32 simd extensions is currently unstable and requires recompiling libcore in order to enable them so in order to take advantage of these in WebAssembly, one has to recompile libcore, typically done by xargo.
I'm trying to enable panic_immediate_abort in order to get smaller wasm size (see rust-lang/rust#54981). The workflow is to create a Xargo.toml file:
However, I can't figure out how to invoke
xargo
when usingwasm-pack build
. I can runxargo build --target wasm32-unknown-unknown --release
, which I assume puts the output in the target directory without compiling it to the pkg directory, but thenwasm-pack build
just overwrites the target directory again with the non-xargo build.The text was updated successfully, but these errors were encountered: