On Mon Oct 6 18:46:16 2025 +0000, Paul Gofman wrote:
FWIW I don't know that anything does depend on these exports, if that is a big deal for dxvk maybe it can wait, but for Wine it is just a matter of using a better fitting 'spec' file entry.
I don't know, this seems to have raised an unexpectedly high amount of discussion for something that looked pretty straightforward to me, and was meant to fix a simple annoying issue:
When using these D3DKMT functions in DXVK, they get resolved by MinGW to dxgi.dll, and when running an application with DXVK, we crash on a missing / stubbed dxgi export (depending on whether DXVK dxgi or Wine dxgi is used).
Exporting these functions and forwarding them where they are supposed to go, like it seems is (or was) the case on Windows (and the reason MinGW exports them), fixes the issue without having to bother with toolchain updates, fragile link library ordering, or other alternative tricks.