Open
Description
openedon Feb 8, 2024
Problem
If trying to build for a target, wasm32-unknown-unknown, for example, and the target is not installed with rustup, cargo will still attempt to build and throw lots of errors which don't have an obvious cause. These are rustc mostly being unable to find items from the standard library.
Proposed Solution
It would be helpful for cargo to check that the correct target toolchain is available and provide and appropriate error message.
Notes
I imagine this isn't an issue for no_std crates, but since that is resolved at the crate level beforehand it should be feasible for cargo to make that determination.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
Area: using --target flag for other platformsArea: using --target flag for other platformsArea: rustup interactionArea: rustup interactionCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Status: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fixStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fix