Closed duhone closed 1 year ago
@juan-lunarg please advise - I can pull a copy of this from VVL when doing the spec updates, if the link above is the correct source. Best to update everything in the same tagged commit, I think.
Although, since VVL itself does not update until sometime after XML changes are published in Vulkan-Headers, in general anything sourced from there is going to lag the spec update.
The file vk_enum_string_helper.h is missing. It seems like every other file in Include\vulkan from the SDK is here, but not this one. For instance, this forces me to use the full sdk github action instead of the lightweight one, since I depend on that file.
Vulkan-Headers has never supplied vk_enum_string_helper.h
. That file currently comes from the vulkan validation layers due to historical reasons.
Although, since VVL itself does not update until sometime after XML changes are published in Vulkan-Headers, in general anything sourced from there is going to lag the spec update.
Yeah it would end up lagging unless you are willing to generate the code in VVL pointing to the new headers. IE it would make your process more complicated. Also we plan to move vk_enum_string_helper.h
to the https://github.com/KhronosGroup/Vulkan-Utility-Libraries instead of living in vvl.
Describe the bug
The file vk_enum_string_helper.h is missing. It seems like every other file in Include\vulkan from the SDK is here, but not this one. For instance, this forces me to use the full sdk github action instead of the lightweight one, since I depend on that file.
Expected behavior the file vk_enum_string_helper.h is included.