Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing cmake version that was broken for iOS builds #15

Closed
wants to merge 1 commit into from

Conversation

dr-orlovsky
Copy link

check rust-lang/cmake-rs#96 for details

@jean-airoldie
Copy link
Owner

jean-airoldie commented Jul 11, 2020

I'm not following. The issue mentions the breaking changes being reverted. Is this still not fixed in the later release?

Assuming this is the case, I think the better solution would be to replace your own dependency with a patch, assuming this will eventually be fixed in the cmake crate. Otherwise this would force the cmake crate version to be exactly "0.1.43" for all the crates using zeromq-src in their dependency tree, since from what I recall, cargo forces one major version per crate, which could lead to problems.

@dr-orlovsky
Copy link
Author

dr-orlovsky commented Jul 26, 2020

Is this still not fixed in the later release?

They are not. They have new release once a year or so...

better solution would be to replace your own dependency with a patch, assuming this will eventually be fixed in the cmake crate

that's exactly what I did

Otherwise this would force the cmake crate version to be exactly "0.1.43" for all the crates using zeromq-src in their dependency tree, since from what I recall, cargo forces one major version per crate, which could lead to problems.

True, but if we follow your suggestion it will mean that the crate is simply broken for everyone, and the patch is a solution just for a single project. Also, with the patch, it will be impossible to publish downstream crates to crates.io - and taking into account the release cycle for cmake-rs this may last for many months.

@dr-orlovsky
Copy link
Author

Not needed anymore since we have #17 for now

@dr-orlovsky dr-orlovsky closed this Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants