Works for me. Please give more details on what you are doing.
Is there any particular reason you are using winelib builds? I no longer test those and it's getting really annoying to support those.
I've been using that since I started with dxvk
What's the prefered method?
Building via mingw as detailed in the readme.
Thanks, looks like the issue comes from https://github.com/doitsujin/dxvk/commit/a9b6421f603db2ebf796969378fa60b85f5da2b3
I added the missing include, but note that I'll probably drop winelib support with the next release (-ish).
Ah pants, was trying to avoid having another toolchain just for this
Now I know it isn't supported I'll look into it, but I'll try and keep winelib working myself for now
Thanks, that's it building fine now
I added the missing include, but note that I'll probably drop winelib support with the next release
That is very unfortunate, mingw is a really heavy dependency.
Hi @FireBurn, I had been using DXVK-winelib too, but after using DWARF2 + LTO to compile on Mingw, my performance was better on Mingw vesus Winelib.
Not to mention that it's even better with the new GCC 9.3.0 update.
@orbea
mingw is a really heavy dependency
Yes, it gets a little heavy, around 976.5 Mb only Mingw:

But, you can use Philip's compilations:
Precompiled binaries and / or binaries compiled on different distros often are not acceptable or usable.
They are Windows builds, so they are always acceptable.
They are Windows builds, so they are always acceptable.
I don't understand what you mean? Normally distros don't ship windows binaries.
I mean they are Windows DLLs.
@ViNi-Arco do you think you could post some information on how you managed to get better performance of dxvk with dwarf2 and lto enabled? Since I couldn't see any difference in performance when building with winelib/gcc wrappers to the binaries provided here!?
d3d11.dllx1 2020-03