Closed ldare373 closed 2 months ago
I am not so good about how cargo deals with semver and upgrades, but I saw this upgrade in 0.12.1 cosmic-text
: https://github.com/pop-os/cosmic-text/commit/b68f4ad5c68c91d76a23cc09f218c2e05fccdc1a regarding the .layout_opt()
and I am seeing here that we use master for cosmic-text: https://github.com/pop-os/iced/blob/master/Cargo.toml#L154. What do you think @mmstick @jackpot51 ?
@l-const We're not using semver for cosmic-text yet: https://github.com/pop-os/iced/blob/master/Cargo.toml#L154. So it's necessary to pin it to a specific commit or version until it's fixed.
cargo update -p cosmic-text:0.12.1
cargo update -p cosmic-text:0.12.1
Still no luck with either project, but I'll try to find a combination of versions that work and post an update later.
cargo update --precise c751217 cosmic-text
seems to work as a temporary solution.
cosmic-text does bump the version appropriately for breaking changes, but libcosmic is currently using the master branch directly (to keep up with the latest changes). I've adapted iced to the cosmic-text API changes.
When building a project using libcosmic, I keep getting the following errors:
I've attached the project's
Cargo.toml
,Cargo.lock
, a Nix flake I'm using for it, and the full output ofcargo build
.I also tried building this project the same way. It builds and runs correctly with the Cargo.lock in the repo, but gives the same errors if built after running
cargo update
.Cargo.toml Cargo.lock flake.nix cargo-build.txt
cargo v1.80.0 (376290515 2024-07-16)