Closed VisualEhrmanntraut closed 4 months ago
does typical cargo update helps?
does typical cargo update helps?
No.
cd examples/winit-example/
cargo build # Failed on lock conflicts
cargo update
cargo build # Should works as expected
No luck rebuilding the lock file.
$ rm Cargo.lock
$ cargo update
Updating crates.io index
error: failed to select a version for `core-graphics`.
... required by package `winit v0.29.2`
... which satisfies dependency `winit = "^0.29"` of package `accesskit_winit v0.16.0`
... which satisfies dependency `accesskit_winit = "^0.16.0"` of package `egui-winit v0.26.2`
... which satisfies dependency `egui-winit = "^0.26.2"` of package `eframe v0.26.2`
... which satisfies dependency `eframe = "^0.26.2"` of package `x`
versions that meet the requirements `^0.23.1` are: 0.23.1
all possible versions conflict with previously selected packages.
previously selected package `core-graphics v0.23.0`
... which satisfies dependency `core-graphics = "^0.23"` of package `cocoa v0.25.0`
... which satisfies dependency `cocoa = "^0.25.0"` of package `eframe v0.26.2`
... which satisfies dependency `eframe = "^0.26.2"` of package `x`
failed to select a version for `core-graphics` which could resolve this conflict
I can also confirm disabling xdg-portal
works.
Reported upstream
Fix upstream did the trick for me in egui example, can you check in your projects? (cargo update should now resolve)
Works for me. Thanks.
rfd/examples/winit-example
egui/examples/file_dialog
w/ rfd 0.13 -> 0.14local project
Disabling default features seems to alleviate the problem. Enabling either
xdg-portal
orasync-std
causes it (both need to be disabled).