-
Notifications
You must be signed in to change notification settings - Fork 48
Could not determine the wanted artifact #141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
What |
Can you post the output of This is most definitely an issue with the unstable features you're using in cargo |
|
Output of
Output of
BTW, |
A few more information that I could provide: The workspace's [workspace]
resolver = "2"
members = ["rmk", "boards/*"]
default-members = ["boards/stm32h7", "rmk"]
cargo-features = ["per-package-target"]
[package]
name = "rmk-stm32h7"
...
forced-target = "thumbv7em-none-eabihf"
[dependencies]
...
[[bin]]
name = "rmk-stm32h7"
test = false
bench = false
|
@Emilgardis @burrbull it seems |
The problem is due to a mismatch on how This seems to be a recent change, I'll see if I can locate it. A fix should be done though, parsing package ids from cargo is in my experience notoriously hard to do properly |
We compare the package ids here: Line 424 in 5c38490
and it fails because |
Aha! rust-lang/cargo#13311 (comment) So, update nightly to atleast |
Also, you may want to specify |
okay! I'll try it later😉 |
When I use
cargo size
I got this error: Could not determine the wanted artifact.My project is a workspace, organized like:
The example1 and example2 has different compile target, both use
src
. So I enabledcargo-features = ["per-package-target"]
andforced-target = "thumbv6m-none-eabi"
in Cargo.toml.cargo size
worked well in the previous Rust nightly version(2023-12-31), but recently I updated Rust to 1.77-nightly(2024-01-17),cargo size
was broken then.The text was updated successfully, but these errors were encountered: