It should alreaby be building the master branch.
In order to change the branch you'd need to change the source URL to point to a specific branch
Search Criteria
Package Base Details: dxvk-git
Package Actions
| Git Clone URL: | https://aur.archlinux.org/dxvk-git.git (read-only, click to copy) |
|---|---|
| Keywords: | dxvk |
| Submitter: | ssorgatem |
| Maintainer: | ssorgatem (niobium93) |
| Last Packager: | ssorgatem |
| Votes: | 21 |
| Popularity: | 0.000000 |
| First Submitted: | 2018-01-24 19:41 (UTC) |
| Last Updated: | 2023-10-16 15:53 (UTC) |
Packages (1)
ssorgatem commented on 2021-02-21 07:50 (UTC)
theriddick commented on 2021-02-21 04:30 (UTC)
Just curious, what would I need to change in the PKGBUILD in order to just build the master branch? there are some critical fixes appearing in master since release of 1.8.
eimis commented on 2020-04-21 12:04 (UTC)
I thank you so much for maintaining this.
PedroHLC commented on 2019-12-16 10:56 (UTC)
Now that d9vk got merged in dxvk, how these two packages will be kept?
silly commented on 2019-02-09 18:20 (UTC)
Shouldn't win packages setup dxgi as well? Assumed it was only the wine packages that could utilize wine's dxgi.
ssorgatem commented on 2018-08-28 06:06 (UTC)
Then you need to take care yourself of satisfying AUR dependencies. Which is going to be a lot of fun for mingw64...
The winelib version should be easier to install.
greencopper commented on 2018-08-28 05:39 (UTC)
I am not using any helper.
ssorgatem commented on 2018-08-28 04:36 (UTC)
@greencopper certainly. What AUR helper are you using? Maybe try the winelib builds (dxvk-wine64-git, dxvk-wine32-git), which don't require mingw64
greencopper commented on 2018-08-28 04:19 (UTC) (edited on 2018-08-28 04:28 (UTC) by greencopper)
error: target not found: mingw-w64-gcc
==> ERROR: 'pacman' failed to install missing dependencies
Shouldn't it get the dependencies automatically?
ssorgatem commented on 2018-08-26 20:17 (UTC)
@SilverSynch upstream doesn't support a setup script anymore. No source is changed behind anyone's back. Upstream provides a winetricks verb that copies both your 32bit and 64bit local builds into your wineprefix. That's not what the setup script did and that is unsuitable for a package of a distribution.
The current solution (packagers rolling their own setup scripts) was proposed by upstream. See the discussion that lead up to it, specifically mentioning the AUR packages: https://github.com/doitsujin/dxvk/issues/572
You can also see why upstream's approach is not suitable for distro packages: by copying instead of symlinking, you have to manually run again the setup verb for each of your wineprefixes every time you update DXVK.
Meanwhile, for upstream, symlinking is not the best option, since it forces the built binaries to stay in the same path, and thus cannot be moved. This is not a problem for distro packages, but it is for users building or downloading DXVK themselves.
If you don't like my approach to the setup scripts, feel free to ignore them and do it manually as you like or edit them to suit you. But if you want to copy DXVK libraries into specific wineprefixes maybe you are better off using Lutris or winetricks rather than this package. I just preserved the old behaviour, because it is advantadgeous to most users of this package.
Pinned Comments
ssorgatem commented on 2018-06-22 06:24 (UTC) (edited on 2019-02-26 15:49 (UTC) by ssorgatem)
This package provides Windows binaries of the DXVK dlls. They work on wine and should work on Windows too. If you don't specifically want Windows binaries and you want to just use DXVK on wine, the winelib package is a better approach and much easier to build (dxvk-winelib-git).
To enable DXVK in a wineprefix, do the following (with the WINEPREFIX variable properly set):
setup_dxvk installIn order to uninstall DXVK from a wineprefix:
setup_dxvk uninstall