-
I have the vulkan SDK installed on my machine, a newer version than the vulkan headers downloaded by VCPKG. If I use vulkan memory allocator, which also depends on vulkan, it appears that the port for vulkan properly finds out that I have the SDK installed and doesn't try to install additional headers, however, when I do this:
suddenly vulkan and vk_video both show up in my vcpkg_installed/triplet/include path. Note if I don't use vulkan-binding, this is not an issue (of course I need vulkan binding) I don't understand what is different about imgui that cause these old vulkan headers from being installed (and also stop my build from working). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The answer to "use system libs* has always been empty overlays.
VMA doesn't pull vulkan port and instead requires you to pull it yourself (IMHO port bug). |
Beta Was this translation helpful? Give feedback.
The answer to "use system libs* has always been empty overlays.
VMA doesn't pull vulkan port and instead requires you to pull it yourself (IMHO port bug).
Imgui properly declares its dependency on vulkan.