Skip to content
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

Install XrApiLayer_conformance_test_layer.json #100

Merged
merged 2 commits into from
Nov 27, 2024

Conversation

fredemmott
Copy link
Contributor

This is missing from at least the Openxr-cts-x64 bundle, and appears to not be installed by CMake

Taken the same approach as https://github.com/KhronosGroup/OpenXR-CTS/blob/devel/src/conformance/conformance_layer/CMakeLists.txt

Without this, validApiLayer fails on all runtimes when using a prebuild CTS bundle.

This is missing from at least the Openxr-cts-x64 bundle, and appears to not be installed by CMake

Taken the same approach as https://github.com/KhronosGroup/OpenXR-CTS/blob/devel/src/conformance/conformance_layer/CMakeLists.txt

Without this, `validApiLayer` fails on all runtimes when using a prebuild CTS bundle.
@CLAassistant
Copy link

CLAassistant commented Nov 26, 2024

CLA assistant check
All committers have signed the CLA.

@rpavlik
Copy link
Contributor

rpavlik commented Nov 26, 2024

Oh good catch! Adding that layer-related test has definitely caused a few glitches on the CTS side of things, thanks for adding this. Can you add a changelog fragment in changes/conformance/pr.100.gh.OpenXR-CTS.md, something like Fix: Install manifest for test API layer? Otherwise I can, since I actually do understand this fix :)

@rpavlik rpavlik merged commit 76d9e3b into KhronosGroup:devel Nov 27, 2024
4 checks passed
@rpavlik
Copy link
Contributor

rpavlik commented Nov 27, 2024

Thank you!

@fredemmott fredemmott deleted the patch-1 branch November 27, 2024 01:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants