On Tue, Jan 22, 2019 at 05:26:08PM +0330, Henri Verbeet wrote:
In the first place, thanks for this.
On Fri, 18 Jan 2019 at 23:11, Andrew Eikum aeikum@codeweavers.com wrote:
+=========== +Using vkd3d +===========
+Vkd3d can be used by projects that target D3D12 as a drop-in replacement at +build-time with some modest source modifications. Or it can be used by Wine to +run Windows applications that target D3D12.
I'd prefer consistently using "Direct3D 12".
Sure.
The Wine bit feels out of place to me. True, Wine is a major user of vkd3d, but vkd3d is also a mostly independent project. This strikes me as something that belongs in the Wine documentation rather than the vkd3d documentation.
Yeah, that's true. I mostly wanted to highlight the awkward circular dependency when building from git. I could see a naive user building all of Wine to get widl, then building vkd3d, and expecting their first Wine build to use vkd3d. I still think it's useful info, but if you disagree, perhaps just explaining the widl build step is enough and we can remove the whole last paragraph. I don't feel strongly.
Andrew