| Git Clone URL: | https://aur.archlinux.org/dxvk-git.git (read-only, click to copy) |
|---|---|
| Package Base: | dxvk-git |
| Description: | A Vulkan-based compatibility layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine. Windows DLL version) |
| Upstream URL: | https://github.com/doitsujin/dxvk |
| Keywords: | dxvk |
| Licenses: | zlib/libpng |
| Conflicts: | dxvk-bin |
| Provides: | d9vk, dxvk |
| Submitter: | ssorgatem |
| Maintainer: | ssorgatem (niobium93) |
| Last Packager: | niobium93 |
| Votes: | 21 |
| Popularity: | 0.000000 |
| First Submitted: | 2018-01-24 19:41 (UTC) |
| Last Updated: | 2024-07-07 15:17 (UTC) |
Both issues should be fixed now.
I no longer trust meson with keeping true to the prefix variable, so I manually put the files in the right place after the "ninja install" step for each version (x32 and x64).
It should now be properly built in release mode now.
@ssorgatem and meson configure in package() doesn't build dxvk in release mode as far as I can tell
Initially it was like that... but ninja install would sometimes ignore the prefix and install to /usr/local instead.
I can look into that though.
I think meson configure commands should be removed from package() function since they trigger full recompilation (but dxvk is already compiled in build() function) Patched PKGBUILD - https://bpaste.net/show/5e4c9852492d
@ssorgatem, thank you very match!!!
There you go, a package for 0.30 that doesn't require a crosscompiler: https://aur.archlinux.org/packages/dxvk-bin/
But there's no point in doing that. People who installed the package before the release would needlessly rebuild and install the same code... and in a few hours this package will be different than the stable release anyway.
It's a -git package; its version should only be updated when changed are made to the PKGBUILD; it's assumed that the development code it build will be changing.
ssorgatem commented on 2018-03-02 11:46 Also, tge release of a new version does not make this package out of date. This builds against the git repository, that means, the latest unreleased code.
You can simply update the package version so that the yaourt discovers a new update.
Help me please. I can't build it. It says there is no file, but in fact this file is in this folder.
Starting build()... The Meson build system Version: 0.44.1 Source dir: /home/user/dxvk-git/src/dxvk Build dir: /home/user/dxvk-git/src/dxvk/build.w64 Build type: cross build Project name: dxvk wine: cannot find '/home/user/dxvk-git/src/dxvk/build.w64/meson-private/sanitycheckc_cross.exe'
Meson encountered an error in file meson.build, line 1, column 0: Executables created by c compiler /usr/bin/x86_64-w64-mingw32-gcc are not runnable.
A full log can be found at /home/user/dxvk-git/src/dxvk/build.w64/meson-logs/meson-log.txt ==> ERROR: A failure occurred in build(). Aborting...
Also, tge release of a new version does not make this package out of date. This builds against the git repository, that means, the latest unreleased code.
Pinned Comments
niobium93 commented on 2024-07-07 15:22 (UTC)
DXVK upstream just merged d3d8 support, so I updated our setup script. Be sure to re-run it to enjoy DXVK's shiny new d3d8 frontend!
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