• Philip Langdale's avatar
    vulkan: add support for win32 handle types · 8dea6887
    Philip Langdale authored
    There are two win32 specific handle types, which we believe to be
    the ones that would be primarily used by a win32 client.
    
    There is the 'NT Handle', which is available on Windows 8 or newer,
    and the 'Global share Handle' (abbreviated as KMT in the Vulkan spec),
    which is available on Windows 7 and newer, but which apparently
    shouldn't be used when the 'NT Handle' type is available. We do not
    attempt to judge usage, and it is up to the client to decide which
    of the two types it wants to use.
    
    Note that the existing logic for identifying the handle_caps is not
    actually sufficient. We need to call specific functions to identify
    what is possible for buffers, images, and semaphores.
    
    * vkGetPhysicalDeviceImageFormatProperties2KHR
    * vkGetPhysicalDeviceExternalBufferPropertiesKHR
    * vkGetPhysicalDeviceExternalSemaphorePropertiesKHR
    
    and these need to be called with the specific flags and parameters,
    so I think it basically ends up being that you can't tell if your
    image/buffer/semaphore is exportable until you create it. Anyway.
    
    I am not in a position to test any of these changes. Someone who
    can build on win32 must do that.
    8dea6887
Name
Last commit
Last update
..
shaders Loading commit data...
utils Loading commit data...
colorspace.h Loading commit data...
common.h Loading commit data...
context.h Loading commit data...
dispatch.h Loading commit data...
dither.h Loading commit data...
filters.h Loading commit data...
gpu.h Loading commit data...
renderer.h Loading commit data...
shaders.h Loading commit data...
swapchain.h Loading commit data...
vulkan.h Loading commit data...