Install full OTIO Python env with CMake #1238
Merged
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.
Currently when setting
OTIO_PYTHON_INSTALL=ON
in CMake, only the compiled Python bindings are installed, which can't be used on their own. This update expands this to match the OTIO PyPI package in the CMake install location, including the three pure-python libs:opentimelineio
,opentimelineview
, andopentielineio_contrib
. The result is that the CMake install is production-ready in a Python env.While on by default when building the Python bindings,
opentimelineview
is also gated behind the existing (and currently unused)OTIO_INSTALL_COMMANDLINE_TOOLS
, andopentielineio_contrib
behind a newOTIO_INSTALL_CONTRIB
option, so both can be turned off if only the core lib is needed.