-
-
Notifications
You must be signed in to change notification settings - Fork 14
Description
I have attached the full build log, but the command I'm using is:
cargo +nightly install cargo-playdate --git=https://github.com/boozook/playdate.git
and it fails with several compilation errors, most of them like this:
error: let chains are only allowed in Rust 2024 or later
--> cargo\src\assets\mod.rs:96:5
|
96 | if let Err(err) = plan::merge_all_virtually(cfg, tree, &plans) &&
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I actually made a fork updating everything to edition 2024 and have it building, but it fails when running tests or when building new playdate projects with errors like this:
Error: failed to load manifest for workspace member `c:\knut\prog\playdate_fork\cargo`
referenced by workspace at `c:\knut\prog\playdate_fork\Cargo.toml`
Caused by:
0: failed to parse manifest at `c:\knut\prog\playdate_fork\cargo\Cargo.toml`
1: feature `edition2024` is required
The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.81.0).
Consider adding `cargo-features = ["edition2024"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.
What's weird is that I have a different version of cargo installed:
>cargo +nightly -V
cargo 1.96.0-nightly (f298b8c82 2026-02-24)
Is it because playdate-cargo is depending on 0.82 instead of a newer version? And therefore moving to Rust 2024 depends on #489 ?
Since I've already started trying to fix this, I might be able to continue, but especially updating the cargo dependency is delving into a lot of stuff I don't know, so I could use some guidance there.
Metadata
Metadata
Assignees
Labels
Projects
Status