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.

Sign up for GitHub

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

Jump to bottom

[vulkan] Allow the user to specify custom Vulkan proc addresses. #3227

Closed
wants to merge 1 commit into from
Closed

[vulkan] Allow the user to specify custom Vulkan proc addresses. #3227

wants to merge 1 commit into from

Commits on May 14, 2020

  1. [vulkan] Allow the user to specify custom Vulkan proc addresses. 

    Some Vulkan applications don't link against libVulkan. Instead, proc addresses
for Vulkan functions are resolved dynamically at runtime. When this is done, all
translation units are compiled with VK_NO_PROTOTYPES defined somewhere and each
Vulkan API callsite looking at a dispatch table. This scheme was incompatible
with the working of imgui_impl_vulkan as specifying VK_NO_PROTOTYPES would cause
compile failures. Now specifying
ImGui_ImplVulkan_InitInfo::GetVulkanProcAddressFn will delegate proc address
resolution responsibilities to the caller. If the caller does not specify this
callback and has not compiled the imgui_impl_vulkan.cpp translation unit with
VK_NO_PROTOTYPES, the proc address table is populated with static addresses as
before. So existing users should not have to change anything.
    @chinmaygarde
    chinmaygarde committed May 14, 2020
    Configuration menu
    Copy the full SHA
    4b2038d View commit details
    Browse the repository at this point in the history