[PATCH v2 vkd3d 1/4] build: Drop hack for stripping RPC includes from widl-generated headers.

[Sveinar Søpler]

>> So, when it comes to creating a installable package like i did with libFAudio, i would need (as you say) libvulkan-headers. Those headers i guess could be patched into the build-source as a external download/dep kind of thingy perhaps?

>Perhaps. The headers are required only to build the package.

Someone with half a debian brain would probably figure out a neat debuild script that would do that. I'm currently at a loss here tho, but won't give up just yet. It is the same with spirv-headers too, as this is not available as a package for all distro's.

>> And then just make wine depend on >libvulkan-1.1.84, and its up to the users to figure that out?

>The version of libvulkan shouldn't matter. It should be possible to build and/or run libvkd3d with pretty much any libvulkan version.

In other words, once built, libvkd3d does not depend on the same libvulkan1 version as the headers, and its mostly up to the driver to provide stuff? And libvkd3d is "extension free" when it comes to libvulkan and driver capabilities?

That said, i was able to build a "widl" package on my PPA for bionic and cosmic, so vkd3d is once again being built for those distro's.

Sveinar

----- Original Message -----
From: "joseph kucia" <joseph.kucia at gmail.com>
To: "Sveinar Søpler" <cybermax at dexter.no>
Cc: "wine-devel" <wine-devel at winehq.org>
Sent: Sunday, April 14, 2019 2:29:14 PM
Subject: Re: [PATCH v2 vkd3d 1/4] build: Drop hack for stripping RPC includes from widl-generated headers.

On Sun, Apr 14, 2019 at 2:02 PM Sveinar Søpler <cybermax at dexter.no> wrote:
>
> There is no such thing as "get those easily from.." when it comes to Luanchpad PPA, or OBS. Cos the ONLY option afaik is either a: From "official" repo's, or b: build yourself so that the package builder have access to it from "itself".
>
> So, when it comes to creating a installable package like i did with libFAudio, i would need (as you say) libvulkan-headers. Those headers i guess could be patched into the build-source as a external download/dep kind of thingy perhaps?

Perhaps. The headers are required only to build the package.

> And then just make wine depend on >libvulkan-1.1.84, and its up to the users to figure that out?

The version of libvulkan shouldn't matter. It should be possible to
build and/or run libvkd3d with pretty much any libvulkan version.

> I dunno if its interesting anyway for WineHQ to build wine-devel with vkd3d support for anything older than the unreleased Ubuntu Disco on their package repo tho. And seeing wined3d making a move towards vulkan might require newer vulkan headers there too?

Wine doesn't require Vulkan headers. Wine has its own Vulkan headers
generated from vk.xml by the dll/winevulkan/make_vulkan script.