Package Details: dxvk-mingw 2.3.1-1

Git Clone URL: (read-only, click to copy)
Package Base: dxvk-mingw
Description: Vulkan-based implementation of D3D9, D3D10 and D3D11 for Linux / Wine, MingW version
Upstream URL:
Licenses: zlib/libpng
Conflicts: d9vk, dxvk
Provides: d9vk, dxvk
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 9
Popularity: 0.046048
First Submitted: 2019-12-16 17:34 (UTC)
Last Updated: 2024-03-21 10:44 (UTC)

Pinned Comments

loathingkernel commented on 2019-12-16 19:48 (UTC) (edited on 2019-12-16 19:49 (UTC) by loathingkernel)

This package contains three patches which are not applied by default. Feel free to read the documentation inside the PKGBUILD on what they do and how to enable them.

Don't report issues with these patches enabled to the dxvk creator before posting here. If you do, please be aware that they will probably close your issue nevertheless.

Latest Comments

1 2 3 4 Next › Last »

loathingkernel commented on 2024-04-17 06:13 (UTC)

@GrabbenD no, because this package builds Windows binaries through cross-compilation. Some compiler and linker options from makepkg.conf are not supported by MingW. So this package cannot use any compiler/linker options from it.

At the same time, because it is meant to be loaded by Wine, certain combinations will interfere with that. As such this package inherits only -march from makepkg.conf at this moment. -O3 is the default from DXVK and that is why it is forced instead of -O2

GrabbenD commented on 2024-04-16 21:48 (UTC)

How come this package forces O3? Isn't it more intuitive to use user's /etc/makepkg.conf (like march=native)?

loathingkernel commented on 2024-04-01 12:31 (UTC)

@reteo you can edit the pkgbuild and replace the first checksum with 'SKIP'

reteo commented on 2024-03-29 19:40 (UTC)

Is there anything I can do to fix this, or should I wait for an update for pacman?

loathingkernel commented on 2024-03-29 13:22 (UTC)

@reteo This is due to recent changes in pacman and Manjaro being outdated.

reteo commented on 2024-03-28 19:48 (UTC) (edited on 2024-03-28 19:49 (UTC) by reteo)

When attempting to install the 2.3.1-1 update, I'm getting the following:

==> Validating source files with sha256sums...
    dxvk ... NOT FOUND
    dxvk-extraopts.patch ... Passed ... Passed
    setup_dxvk ... Passed
==> ERROR: One or more files did not pass the validity check!

loathingkernel commented on 2023-06-09 12:29 (UTC)

@patlefort, good lord, there is no consistency with that repo... also hosting tarballs in the git repo? what the hell. I low key feel like I don't want to adapt to it as a protest. The handling is just stupid...

patlefort commented on 2023-06-09 12:12 (UTC)

dxvk async patches have moved to a patches subdir:

monarc99 commented on 2023-03-07 02:56 (UTC)

async dxvk patch for 2.1:

loathingkernel commented on 2022-12-08 12:34 (UTC) (edited on 2022-12-08 12:36 (UTC) by loathingkernel)

@AvianaCruz That's a paru problem, not a PKGBUILD problem.

There is nothing in the wiki about pinning submodule commits (not only that, but git will resolve the correct commits on its own) but also official PKGBUILDS from the repos don't do that.

There is a clearly defined way for PKGBUILDs to indicate that something is supposed to build a VCS version of a package and that is the suffix in the package name. I don't see why paru tries to be smart and accommodate for bad package names.