ClamAV found Win.Trojan.Virut-53 in the latest update, specifically in 32-bit d3d11.dll.
Upstream already aware, false positive, https://github.com/doitsujin/dxvk/issues/5762
| Git Clone URL: | https://aur.archlinux.org/dxvk-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | dxvk-bin |
| Description: | A Vulkan-based compatibility layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine (Windows DLL binary files) |
| Upstream URL: | https://github.com/doitsujin/dxvk |
| Keywords: | dxvk |
| Licenses: | zlib/libpng |
| Conflicts: | d9vk, dxvk |
| Provides: | d9vk, dxvk |
| Submitter: | ssorgatem |
| Maintainer: | ssorgatem (kekonn) |
| Last Packager: | kekonn |
| Votes: | 239 |
| Popularity: | 3.14 |
| First Submitted: | 2018-03-02 07:39 (UTC) |
| Last Updated: | 2026-07-18 06:53 (UTC) |
ClamAV found Win.Trojan.Virut-53 in the latest update, specifically in 32-bit d3d11.dll.
Upstream already aware, false positive, https://github.com/doitsujin/dxvk/issues/5762
@kode54 Maybe add wine as well, for good measure. The script is invoking wine commands anyway.
Also, my suggestion is based off the fact that installing the resulting package on a fresh system (no base-devel) generates the error when running the script. Shouldn't a similar check already be enforced when submitting to the AUR?
@inutakhan which is included in base-devel, which is implied by any AUR packaging as a bare minimum.
Edit: Oh. Maybe add it as a runtime dependency, since it's needed to use it after packaging.
Odd. I don't have which installed on my machine. Maybe add that as a dependency? setup_dxvk invokes the command.
With the recent changes in Wine, namely this commit, the packaged setup_dxvk script fails for regular wine too now, not only wow64. I am currently aware of two scripts that should work with current Wine, this is the one I use and this one from dxvk-msvc-git.
Feel free to use whichever you prefer, but please update it.
They are correct that the old upstream script doesn't work if wine has been built using the new wow64 wine mode. Feel free to take the updated script from dxvk-mingw AUR package.
@Piroro-hs the setup script is working as expected for me, both with and without the "--symlink" option. The x32 libraries are put in c:/windows/syswow64/
The setup_vxdk script plays poorly with wow64 wine. It copies x64 dlls to C:\windows\system32 then overwrite those with x32 dlls.
@Lili1228: should be fixed now
Please update setup_dxvk to include d3d8.dll that was added in 2.4.
Pinned Comments
ssorgatem commented on 2018-03-27 06:47 (UTC) (edited on 2019-02-26 12:20 (UTC) by ssorgatem)
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