Support both OpenGL and Vulkan Hgi from single build. #2564
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-8554 |
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)
Makes it possible to use hgiOpenGL or hgiVulkan from a single USD distribution, with the choice to use which happening at runtime.
Fixes Issue(s)
Currently only a single OpenGL, Vulkan, or Metal backend is built with USD. While the exclusionary nature of OpenGL/Metal makes sense for macOS, this is less true for Window or Linux and means an app cannot choose which to use at runtime in addition to making updating a render-delegate to be aware of hgiVulkan a bit more difficult than it needs to be.
Additionally, with proposals such as Autodesk DirectX backend, it makes sense to think of these interop plug-ins as a matrix where multiple backends can transfer to one-another as needed.