Still detect boost, even if boost-python is not available#1321
Merged
Still detect boost, even if boost-python is not available#1321
Conversation
mamoll
approved these changes
Sep 23, 2025
Member
|
Thanks for the fix! |
saahu27
pushed a commit
that referenced
this pull request
Oct 3, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On systems with boost-python missing, the feature-summary otherwise fails to detect Boost after successfully detecting it further above.
As explained in the comment this is because
find_boost_pythoninternally usesfind_package(Boostwith different components as well and these inner calls can overwrite detected variables, specificallyBoost_FOUND.