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 +stable metadata
<snip>
❯ cargo +beta metadata
error: failed to parse manifest at `/tmp/Cargo.toml`
Caused by:
failed to parse `x86_64/windows.json` as a cfg expression: invalid target specifier: unexpected character / in target name
The text was updated successfully, but these errors were encountered:
This is a result of a change in the parsing code in #7375. However, this hasn't worked in a long time (if ever?), as the target was an absolute, canonicalized path. Then, in #7425 it was changed to be the file stem.
So a target like --target foo/bar.json now matches the platform in [target.bar.dependencies].
@alexcrichton Does the current behavior (file_stem) seem like the correct choice? If so, this seems like a documentation change (and adding a test).
According to https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#platform-specific-dependencies, custom target specification is allowed, e.g.
cargo +stable metadata
works on this toml, whilecargo +beta metadata
failsThe text was updated successfully, but these errors were encountered: