APPLE: Streamline Framework build headers#3714
Open
dgovil wants to merge 5 commits intoPixarAnimationStudios:devfrom
Open
APPLE: Streamline Framework build headers#3714dgovil wants to merge 5 commits intoPixarAnimationStudios:devfrom
dgovil wants to merge 5 commits intoPixarAnimationStudios:devfrom
Conversation
10 tasks
dgovil
changed the title
Collaborator
|
Filed as internal issue #USD-11202 (This is an automated message. See here for more information.) |
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.
Description of Change(s)
This PR allows for Framework builds (requires #3713 to be merged first) to use modified headers such that the frameworks can easily be used in Xcode or via
-framework OpenUSDwithout any extra configuration.It does so by modifying headers in the framework by changing them to
<OpenUSD/pxr/pxr.h>instead of<pxr/pxr.h>.These headers then work without having to configure anything, but if a developer were to also add the header search path, then they could use either form interchangeably too.
Of course, any code that uses the prefixed header format could not be used portably with a codebase that doesn't prefix its headers, so the option is opt-in.
Checklist
I have created this PR based on the dev branch
I have followed the coding conventions
I have added unit tests that exercise this functionality (Reference:
testing guidelines)
I have verified that all unit tests pass with the proposed changes
I have submitted a signed Contributor License Agreement (Reference:
Contributor License Agreement instructions)