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
> cargo web deploy
warning: debug builds on the wasm32-unknown-unknown are currently totally broken
forcing a release build
Finished release [optimized] target(s) in 0.60s
Garbage collecting "frontend.wasm"...
Processing "frontend.wasm"...
Finished processing of "frontend.wasm"!
The `frontend` was deployed to "D:\\projects\\myproject\\target\\deploy"!
But I want to pass --release so that when this issue is fixed and release builds work, it will build with -release and wont accidentally deploy a debug build. So I tried cargo web deploy --release but:
> cargo web deploy --release
Compiling stdweb v0.4.8
error: Could not compile `stdweb`.
error: build failed
But why does it work without --release then, if that command actually does a release build? Shouldn't it behave the same then?
I also noticed the first time I passed --release it compiled all the deps again, even though the normal build should have already built the release versions of the deps, right?
The text was updated successfully, but these errors were encountered:
But why does it work without --release then, if that command actually does a release build? Shouldn't it behave the same then?
There is one difference between --target=wasm32-unknown-unknown --release and just --target=wasm32-unknown-unknown - compiling without --release emits debug info by default.
But I want to pass
--release
so that when this issue is fixed and release builds work, it will build with-release
and wont accidentally deploy a debug build. So I triedcargo web deploy --release
but:rustc.exe crashes every time:
Like in #120
But why does it work without
--release
then, if that command actually does a release build? Shouldn't it behave the same then?I also noticed the first time I passed
--release
it compiled all the deps again, even though the normal build should have already built the release versions of the deps, right?The text was updated successfully, but these errors were encountered: