Omit Python data installation in non-Python builds #1437
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.
Since the addition of Include standard data libraries in Python package #1237, we now create a python folder, with a copy of the stdlibs, even if we're not building python.
This is at best redundant, and in my particular case, caused a problem in a downstream build script.
Also - I noticed that the contents of
<INSTALL>/python/MaterialX/libraries
mirrors the contents of<INSTALL>/libraries
, EXCEPT that<INSTALL>/python/MaterialX/libraries/mdl
is missing. Is this intentional? Should we be copying themdl
folder as well?