-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[openxr-loader] Update to latest version, official repo #12060
Conversation
@jherico |
Have you tested the feature |
My understanding was that the Vulkan port only checked for the presence of the Vulkan SDK. I've tested it with the x64-windows and x86- windows triplets, but not x64-windows-static. |
Yes, your understanding is right. Thanks for your update. |
I've checked on x64-windows-static via |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@jherico
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great :)
Co-authored-by: NancyLi1013 <[email protected]>
LGTM now. Thanks for your hard work. @jherico |
Thanks for your contribution! |
) Co-authored-by: NancyLi1013 <[email protected]>
Describe the pull request
Updates the OpenXR loader to the most recent released version, 1.0.11
Additionally, the loader was previously being built from a fork to include the
openxr.hpp
header. The hpp header is an official OpenXR Khronos project, but it's not currently integrated into the build of the OpenXR SDK itself. In order to work around this I previously used a fork where I manually included the header, but Vcpkg practices suggest it's preferable to make such modifications via patch or change to the portfile.This this PR switches the port to use the official Khronos repository for the OpenXR SDK. Additionally at build time it also clones the required repositories to build the
openxr.hpp
file, and also includes a small patch file to correct a bug in the generated header.The onus is therefore on the port maintainer to ensure that when they update the version of the OpenXR loader, they also update the refs of the additional repositories to match. The
OpenXR-SDK-Source
repo should have the same version tags as the mainOpenXR-SDK
repo, but theOpenXR-hpp
repo doesn't use version tags and should just use the current HEAD. The port maintainer should also ensure that the patch file is updated as necessary or removed once the bug is fixed in the upstream repository.ARM and UWP based triplets are not supported. This represents no change from the existing version.
Yeah, I think