Add Python version to pxrConfig.cmake #2093
Merged
Conversation
This file contains 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
|
Filed as internal issue #USD-7778 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Change(s)
These proposed changes address the problem of how to configure another downstream cmake-based project that depends on USD, on systems with multiple versions of Python installed. The solution is to stash in the generated
pxrConfig.cmakefile the exact version used at build time, for the other projects to find, if possible. The build script can now help with that.Fixes Issue(s)
find_package(Python)inpxrConfig.cmakemay not find the correct version of Python for another downstream project to successfully build. To be correct,find_package(Python <version> EXACT)is needed, with<version>the version of Python that USD was built with.