error: No packages has been produced, nothing to run. #315
Comments
|
Would you reproduce it with additional args |
|
|
|
|
|
|
|
This is the output of |
|
I need to finish up for the night but the little debugging I've done reveals that after the following, playdate/cargo/src/build/mod.rs Lines 72 to 73 in e334325 |
|
After this, playdate/cargo/src/build/mod.rs Line 261 in e334325 |
|
After this: playdate/cargo/src/build/mod.rs Line 292 in e334325
[
(
Package {
id: PackageId {
name: "hello-world",
version: "0.1.0",
source: "/Users/py/projects/paulyoung/hello-world",
},
..: "..",
},
[
TargetInner {
..: lib_target("hello-world", ["staticlib", "dylib", "rlib"], "/Users/py/projects/paulyoung/hello-world/src/lib.rs", Edition2021),
},
],
),
] |
|
Here: playdate/cargo/src/build/mod.rs Line 298 in e334325
|
|
If I use the nightly build I was using before ( |
|
Possibly related to rust-lang/cargo#12783 which |
|
Wow! Great investigation! 😲 |
|
Okay, I've reproduced it easily with just |
boozook
added a commit
that referenced
this issue
Apr 22, 2024
…d artefact name format - now replaces dashes with underscores for libs too.
|
Hey Paul, could you plz test your case with that branch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #278 (comment) I said:
I was mistaken. I hadn't saved the change to upgrade Rust so was still using
2023-12-28. With2024-04-12I get this error for both device and simulator:The text was updated successfully, but these errors were encountered: