[PATCH vkd3d 05/10] vkd3d: Enable VK_EXT_vertex_attribute_divisor.

[Jens Reyer]

On 10/25/18 2:15 PM, Alexandre Julliard wrote:
> Józef Kucia <joseph.kucia at gmail.com> writes:
> 
>> From: Józef Kucia <jkucia at codeweavers.com>
>>
>> Signed-off-by: Józef Kucia <jkucia at codeweavers.com>
>> ---
>>  libs/vkd3d/device.c        | 24 ++++++++++++++++++------
>>  libs/vkd3d/vkd3d_private.h |  1 +
>>  libs/vkd3d/vulkan_procs.h  |  2 ++
>>  3 files changed, 21 insertions(+), 6 deletions(-)
> 
> This doesn't build on Debian, since it still has vulkan 1.1.73. Do we
> need to ship our own headers?

[ I'm not member of the respective Debian packaging team, haven't worked
on current Wine versions since they use vulkan, and barely know what
vulkan is all about.  The following is only what I just found out: ]

It seems the old vulkan upstream repository[1] was split after the
1.1.73 release:

https://github.com/KhronosGroup/Vulkan-Headers
https://github.com/KhronosGroup/Vulkan-Loader
https://github.com/KhronosGroup/Vulkan-ValidationLayers
https://github.com/KhronosGroup/Vulkan-Tools

Debian already has a new package "vulkan-headers"[1].  Is that all we
need for building Wine?

vulkan-headers in Debian is at version 1.1.82.0-1 (packaged 3 weeks
after the upstream release).  The next and current upstream release
1.1.85 was 3 weeks ago.  So I assume it might appear very soon in
Debian, otherwise we can file a wishlist bug.

There will also be "vulkan-loader" (1.1.82.0-1).  No idea if this is
needed for Wine.  But it's waiting in Debian's NEW-queue[3] since a
month.  Once it has been accepted it will be in the archive (the current
upload targets only experimental).  Future uploads will then go straight
to the archive.

Hope that helps.  I'm now doing a test build of 3.18 with vulkan-headers
instead of vulkan, but that might take a while.

Greets
jre

[1] https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers
[2] https://tracker.debian.org/pkg/vulkan-headers
[3] https://ftp-master.debian.org/new.html