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

Revert "cmake: fix breaking build tree on version/revision bumps" #198775

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

akretz
Copy link

@akretz akretz commented Nov 23, 2024

This reverts #197088 and fixes #198772. The reason for this workaround has been merged upstream into the dev branch already and will be part of the next release #84312 (comment). Not breaking builds has a higher priority than a convenience feature, so I think this patch should be reverted asap.

Also fixes ceres-solver/ceres-solver#1118

  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

@github-actions github-actions bot added the autosquash Automatically squash pull request commits according to Homebrew style. label Nov 23, 2024
@github-actions github-actions bot removed the autosquash Automatically squash pull request commits according to Homebrew style. label Nov 23, 2024
Copy link
Contributor

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

@SMillerDev
Copy link
Member

Can we use the patch that was merged upstream instead?

@akretz
Copy link
Author

akretz commented Nov 24, 2024

Can we use the patch that was merged upstream instead?

That's possible. I've tried to apply the fix
Kitware/CMake@87cb303...0994bc7
directly on 3.31.1, but it failed with conflicts. So I've resolved them and pushed it onto my fork. I've also had to cherry-pick the helper function
Kitware/CMake@2503b43
which it depends on.

This reverts commit d69d982.
@akretz
Copy link
Author

akretz commented Nov 24, 2024

Actually, the upstream patch also fails on my minimal example of #198772, so I removed it again. The interesting thing is that exactly the same patch works when I build CMake not using brew. So right now the situation with regards to that minimal example is

3.31.1 3.31.1 patched
Build independently
Build brew formula

Probably @carlocab has a better insight on what is going on.

@carlocab
Copy link
Member

Actually, the upstream patch also fails on my minimal example of #198772, so I removed it again.

If I'm understanding this correctly: it seems like this needs to be reported upstream then. Because we can revert #197088 now, but that's just going to break again when upstream changes regarding symlink handling land in a CMake release.

Can you try building cmake from their master branch to double-check that you see the problem from #198772 there?

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.

CMake doesn't find packages properly Error detecting Eigen3_VERSION
3 participants