(Edit) Which C++ versions should Vulkan spec repo test Hpp headers against?
envgap__KhronosGroup__Vulkan-Hpp-2237
01 / FAILURE SIGNATURE
As reported upstream
that gets compiled against the headers built from Vulkan-Hpp as part of CI. I'm not sure why this did not fail in e.g. https://github.com/KhronosGroup/Vulkan-Docs/actions/runs/16665603415/job/47171453856 (much less the internal gitlab CI which should have caught it earlier). @asuessenbach could you look at the test file and see if there's any apparent reason it would not have compiled vulkan_structs.hpp and found the error, like the Vulkan-Headers test did?
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
6b28af9f1ffac2c9fae0b9b3ff0cc335f2da473c- Manifest
CMakeLists.txt- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
KhronosGroup/Vulkan-Hpp #2237 · read the original issue
There's a simple test in https://github.com/KhronosGroup/Vulkan-Docs/blob/main/tests/hpptest.cpp that gets compiled against the headers built from Vulkan-Hpp as part of CI. I'm not sure why this did not fail in e.g. https://github.com/KhronosGroup/Vulkan-Docs/actions/runs/16665603415/job/47171453856 (much less the internal gitlab CI which should have caught it earlier). @asuessenbach could you look at the test file and see if there's any apparent reason it would not have compiled vulkan_structs.hpp and found the error, like the Vulkan-Headers test did?
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]