Package Details: dxvk-wine64-git 0.90_4_ge0e945f-1

Git Clone URL: (read-only)
Package Base: dxvk-wine-git
Description: A Vulkan-based compatibility layer for Direct3D 10/11 which allows running 3D applications on Linux using Wine. Winelib version
Upstream URL:
Licenses: zlib/libpng
Conflicts: dxvk-bin, dxvk-git, dxvk-win64-bin, dxvk-win64-git
Provides: dxvk, dxvk64
Submitter: ssorgatem
Maintainer: ssorgatem
Last Packager: ssorgatem
Votes: 2
Popularity: 0.153045
First Submitted: 2018-07-22 16:53
Last Updated: 2018-10-16 10:52

Pinned Comments

ssorgatem commented on 2018-07-22 17:00

These packages use a winelib build of DXVK instead of a Windows build. This means they are built as a wine library rather than a Windows DLL. Therefore, they do not need a crosscompiler to be built.

They can replace the dxvk-win-git and dxvk-win-bin packages. Be sure to re-run the setup_dxvk64 script if switching over from those.

Both 64-bit and 32-bit DXVK packages are available.

Latest Comments

1 2 Next › Last »

ssorgatem commented on 2018-12-05 09:04

@Sukid it builds fine on my end. Maybe you are missing some headers?

Which compiler are you using? I think you need to use the same you used to build wine. So if you use wine built with GCC, use GCC.

I couldn't build with GCC against a Clang-built wine.

Sukid commented on 2018-12-05 03:13

Getting a lot of /usr/include/c++/8.2.1/cmath:45:15: fatal error: math.h: No such file or directory #include_next <math.h> and /usr/include/c++/8.2.1/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next <stdlib.h>

resulting in compiling not working. What changed?

ssorgatem commented on 2018-10-16 10:50

@zfkerr thank you! Should be fixed now.

zfkerr commented on 2018-10-15 16:20

Hi, @ssorgatem ! I found a bug in your PKGBUILD, which leads to the appearance of one extra slash in /usr/bin/setup_dxvk **

   _package_dxvk() {
    if [ "$1" = "32" ]; then

It should be correct like this:

_package_dxvk() {
    if [ "$1" = "32" ]; then

loathingkernel commented on 2018-08-28 17:12

It was my mistake, I was working with a PKGBUILD that I had already edited and didn't remember about it. Sorry for the noise.

ssorgatem commented on 2018-08-28 17:08

@loathingkernel nope, they aren't there.

Or tell me the line number?

What I'm seeing is quite different:

" conflicts=("dxvk-win64-bin" "dxvk-win64-git" "dxvk-git" "dxvk-bin") provides=("dxvk" "dxvk64") optdepends=('dxvk32: 32-bit support')"

" conflicts=("dxvk-win32-bin" "dxvk-win32-git" "dxvk-git" "dxvk-bin") depends=('lib32-vulkan-icd-loader' 'wine>=3.14' 'winetricks') optdepends=('dxvk64: 64-bit support') provides=("dxvk" "dxvk32")"

ssorgatem commented on 2018-08-28 17:01

Where are you getting those lines from? I can't find them on the PKGBUILD.

But, incidentally, I spotted a typo (the 32-bit package providing "dxvk64" instead of "dxvk32")

gee commented on 2018-08-17 16:31

You probably know of this, but in case you do not:

I'm hopeful we're still able to keep symlinks :)


ssorgatem commented on 2018-07-31 05:02

Yes, that is the plan, as soon as it's supported upstream. The DXVK support for 32-bit already exists (not merged yet), but it relies on a patch in wine.


gee commented on 2018-07-31 04:38

Thank you for this, I tried the standard with mingw and got so many errors in various packages, it was annoying, but this worked right away.

Will you eventually add 32b?