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
Breakage in vulkan-tools and metacity with vulkan-headers-1.2.140 #117
Comments
Fixes build of metacity and vulkan-tools, since both of these rely on VK_DYNAMIC_STATE_RANGE_SIZE being set which was removed in 0c5351f5e9114d3e9033aeae51d036a3d201c082 from vulkan-headers Upstream issue: KhronosGroup/Vulkan-Headers#117 fixes #11503
I'm sorry for the breakage. We did the best we knew how reaching out in multiple formats and forums but obviously these projects didn't get the message. Note that these tokens are explicitly not part of the Vulkan API, which is why they were removed. If you absolutely must have them for some reason then there is a procedure defined in KhronosGroup/Vulkan-Docs#1230 and in the Vulkan-Docs ChangeLog.txt for 1.2.140 telling you how to build headers with these tokens yourself, but we will not be restoring them to the Khronos-supplied headers. |
I opened an issue against Vulkan-Tools repo where one use in sample code was overlooked. I don't know anything about metacity and don't have accounts on the relevant git servers, so suggest @Cogitri open an issue there to resolve that problem. |
Alrighty, I'll look into the other projects, thanks. |
Hello,
in vulkan-headers-1.2.140 the definition of
VK_DYNAMIC_STATE_RANGE_SIZE
has been removed, which breaks building packages such as vulkan-tools and metacity (and possibly more). Alpine Linux had to revert back to vulkan-headers-1.2.139 for the time being due to that [0].0: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/7601
The text was updated successfully, but these errors were encountered: