The build script assumes that rustup is always in `~/.cargo/bin/`

[drozdziak1]

What's happening?

Our build script installs the toolchains necessary for each supported platform. It seems to call rustup directly via $HOME/.cargo/bin/rustup which isn't always its correct location.

Why's that a problem?

Someone might have rustup already installed in a non-standard setup of their choosing (Rustup's install script lets you customize the install so that's entirely possible). This causes the build to fail because of No such file or directory being returned when the build tries to run Rustup that way.

Solutions

The easiest solution would most likely be refering to just rustup instead of the full path within the build scripts

[jkilpatr]

the alternative is modifying someone's path for them. I guess the easy installer should do that as a matter of course though.