How to have wasm32-unknown-unknown and x86_64-unknown-linux-musl both available in a Rust project? | Railway | Page 1

wild cedar Apr 12, 2023, 11:57 AM

#

I am trying to build a Rust frontend/backend monorepo and deploy it to Railway. I use yew for the front-end and axum for the back-end. However, building the web-assembly for the frontend fails, because wasm32-unknown-unknown target is not available. So I tried adding a rust-toolchain.toml file and declaring both targets. But that causes musl and musl-dev not to be included in nixPkgs, which causes the backend build to fail. I also tried removing the rust-toolchain.toml and declaring the rust toolchain overrides under "setup" or "phases.setup" in my railway.toml, but that key seems to be ignored. Any help would be appreciated!

hidden currentBOT Apr 12, 2023, 11:57 AM

#

Project ID: d917b9da-1097-4511-9d45-103ec687b97a

wild cedar Apr 12, 2023, 11:58 AM

#

d917b9da-1097-4511-9d45-103ec687b97a

hidden currentBOT Apr 12, 2023, 11:58 AM

#

Try putting rustup target add wasm32-unknown-unknown somewhere in the project, and then build the project with cargo build --release --target x86_64-unknown-linux-musl.

wild cedar Apr 12, 2023, 12:00 PM

#

Thanks, I'll try adding to to my buildCommand and see whether that helps.

#How to have wasm32-unknown-unknown and x86_64-unknown-linux-musl both available in a Rust project?