On Mon Oct 6 19:15:01 2025 +0000, Rémi Bernon wrote:
Like described in the patch, dxgi on Windows 10 doesn't export them anymore, but it was on Windows 8.1. And as MinGW import lib has them, and until they get removed from there, and until the toolchain update is widespread enough, it doesn't seem like a huge deal to have them too. Regarding what these duplicated functions do, I don't think it's interesting at all and I'm not going to spend time looking into this. They are probably just wrappers around the syscalls because they didn't want to pull gdi32 or win32u directly. It's also IMO inconvenient if all these concerns are now requiring us to use GetProcAddress everywhere, just to make sure we get the gdi32 function. I had this initially to workaround the issue but it's not a nice solution and I would even expect it to be slowing down the adoption of D3DKMT for shared resources in DXVK because there's no good reason to have to do it when linking is supposed to just work. Then I would like to add that even though this MR adds new dxgi exports, several of the d3d11 D3DKMT forwards were already present before, and they didn't raise the same concerns that were raised here (and even, some exports have been added which were never supposed to be there).
FWIW I only suggested not using forward import in Wine patch if that is not the case on Windows (it probably isn't). Does it not work for some reason?