Home Creators Posts Import Register Favorites Logout

Content

There where no changes to wine-staging for this release.


Checkout the wine announcement for details on this major release.

https://www.winehq.org/announce/6.0


Big thanks to everyone for your support.

Comments

Simone Garzieri

Hi, I was trying to use the new vulkan backend with no success, the error shown says:"wine wasn't build with libvkd3d-shader". I usually install wine staging through the ppa, because I can't stand the burden to compile it myself. Is it possible to have a binary built with libvkd3d-shader? Thanks for your efforts and I'm amazed by the performance of this amazing project. Have a nice day and thanks for all your support and courtesy.

winestaging

The staging team isn't in control of the building the packages. Are you installing from the winehq repositories or the Ubuntu PPA?

winestaging

I've just had a quick look, and it appear that the official wine builds don't have libvkd3d-shader support. Currently following up on this.

winestaging

It's confirmed that the vkd3d isn't part of the installer for Debian and some of the Fedora packages. Its appears that Debian at least only has vkd3d 1.1 avialable and wine requires 1.2. Will post when I have more information.

Simone Garzieri

Thanks for the update and your quick response. I've managed to compile vkd3d from the latest git repository, I have libvkd3d-shader on my system now (linux mint 20.1) and wine detects it. My problem is that installing the vkd3d 32 bit build in a custom path, prevents wine 32 bit to detect the library. VKD3D_SHADER_LIBS=32 bit vkd3d path doesn't work wine just detects the 64 bit library, installed in the default path, and not the 32 bit version installed in the custom path. Both library can not be installed in the default path at the same time one overwrite the other. Does wine need libvkd3d-shader.so.1 to be constantly installed in the system, in order to use its features, or is it only necessary during wine's compilation phase?

winestaging

It's required it at runtime. Last time I built it locally, these are the configure arguments I used (It does override the installed version, which is what I wanted). ../configure --libdir=/usr/lib/i386-linux-gnu/ CC=i686-w64-mingw32-gcc --host=i386-linux-gnu 64 bits. ../configure --libdir=/usr/lib/x86_64-linux-gnu/

Simone Garzieri

Hi compiling vkd3d 32 bit with CC=i686-w64-mingw32-gcc option give me the error vulkan.h not found. compling vkd3d without the option works but wine 32 still doesn't detect it anyway. 64 bit build of both vkd3d and wine work like a charm. Thanks for your quick support and courtesy. Since I'm not a tech savvy I think I'll wait until the compilation process is more automated, just the way it is for 64 bit compilation. thanks anyway

Simone Garzieri

Hi again I fixed the issue, I copied the build option written in the pkgbuild file of lib32 libvkd3d(it's an arch linux library). On ubuntu/linux mint to compile libvkd3d 32 bit correctly one must give this inputs ./configure --prefix=/usr --libdir=/usr/lib32 CC="gcc -m32" CXX="g++ -m32" PKG_CONFIG_PATH='/usr/lib32/pkgconfig' . For 64 build ./configure is enough. Now both the 32 bit version and the 64 bit version of libvkd3d-shader can coexist at the same time. Wine 32 and 64 bit detects the library correctly, I can't wait to test the new and improved wined3d vulkan backend. Thanks for your support and courtesy kind as usual have a nice day