You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report, and sorry for the frustrating situation.
It appears that one of our dependencies has started requiring that cmake be available, per the error message: is cmake not installed?
Unfortunately, it doesn't seem to me like we have any great options here:
We don't directly depend on that library — it's a transitive dependency somewhere deep in the tree — so we can't easily drop it.
There's no way to specify to cargo that cmake is required. If cmake isn't available, cargo install will simply never work — it cannot install cmake automatically nor proactively error out with a good error message if it isn't available.
We could document that cmake is needed in our README, but since this is a transitive dependency, that requirement might drift over time. And the README is probably not something people will check before running cargo install anyway.
We already provide a prebuilt binary for aarch64-apple-darwin which users are encouraged to use. But obviously some users will prefer to compile the tool themselves, so there's still a problem.
So I had a look at the repository for libz-sys if there is a known issue for that and I found rust-lang/libz-sys#93. It's not directly related but installing cmake via brew install cmake as mentioned over there fixes the error for me.
Most people might have cmake already installed so feel free to close, or maybe have an entry in the FAQ that mentions that?
Steps to reproduce the bug with the above code
Run the following command:
cargo install cargo-semver-checks --version 0.24.0
.Trying to install older versions work fine.
Actual Behaviour
Expected Behaviour
The build should succeed.
Generated System Information
Software version
cargo-semver-checks 0.22.0
Operating system
macOS 14.4 (Darwin 23.4.0)
Command-line
cargo version
Compile time information
Build Configuration
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: