Add support for Boost_NO_BOOST_CMAKE=ON for Boost::python #912
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.
This PR is a reflection of our internal changes to support Boost_NO_BOOST_CMAKE=ON for using boost::python along custom paths.
For a set of Boost Versions, the CMake setup made it difficult to use your own Boost library paths.
Prior to Boost 1.70, certain versions of CMake failed to find Boosts Python library due to the addition of version suffixes.
From Boost 1.70 onwards, it is possible for Boost to optionally support CMake files, but can also be problematic if you want to sub in your own paths. Occasionally without Boost_NO_BOOST_CMAKE, CMake will resolve to other versions of boost even if you specify an explicit boost root path. Hence the need for Boost_NO_BOOST_CMAKE.
See https://stackoverflow.com/a/63094072 for more details.
This doesn't appear to affect any other of the Boost requirements for Maya USD, and so we only manage that one specific library here.