Package Details: lib32-libdxvk 2.3-1

Git Clone URL: https://aur.archlinux.org/libdxvk.git (read-only, click to copy)
Package Base: libdxvk
Description: Native Linux port of DXVK to allow usage without WINE (32-bit)
Upstream URL: https://github.com/doitsujin/dxvk
Licenses: zlib
Provides: libdxvk, libdxvk_d3d11.so, libdxvk_d3d9.so, libdxvk_dxgi.so
Submitter: DavidHusicka
Maintainer: eclairevoyant
Last Packager: eclairevoyant
Votes: 2
Popularity: 0.000035
First Submitted: 2021-08-11 14:46 (UTC)
Last Updated: 2023-09-06 00:43 (UTC)

Pinned Comments

eclairevoyant commented on 2023-01-29 02:30 (UTC)

Adopted and updated. From this point on rather than using tarred releases, I will use the signed release tags (as per guidelines), which allows for PGP signature verification. Therefore, you will need to import the dev's signing key from GitHub or a keyserver (e.g. https://keyserver.ubuntu.com/).

Latest Comments

1 2 Next › Last »

eclairevoyant commented on 2023-05-22 20:14 (UTC)

I don't know what any of that means other than I can't really help you then.

Baerbeisser commented on 2023-05-22 20:10 (UTC) (edited on 2023-05-22 20:11 (UTC) by Baerbeisser)

I'm on Artix, which has now independent repos. Can i fix this myself in the PKGBUILD?

eclairevoyant commented on 2023-05-22 19:40 (UTC)

switched to tag revision per guidelines, if that doesn't fix it you might have to delete your local cached copy of the repo

Baerbeisser commented on 2023-05-22 19:31 (UTC)

Huh, now it says

==> Verifying source file signatures with gpg...
    dxvk git repo ... Passed
==> Extracting sources...
  -> Creating working copy of dxvk git repo...
fatal: invalid reference: v2.2
==> ERROR: Failure while creating working copy of dxvk git repo
    Aborting...

jorgicio commented on 2023-05-04 04:28 (UTC)

Hi.

Since GCC is updated to 13 version, this patch is needed in order to build this package.

https://github.com/doitsujin/dxvk/commit/1a5afc77b1859e6c7e31b55e11ece899e3b5295a.patch

eclairevoyant commented on 2023-02-06 06:03 (UTC)

https://stackoverflow.com/questions/16158158/what-is-the-public-url-for-the-github-public-keys

Baerbeisser commented on 2023-02-05 16:21 (UTC) (edited on 2023-02-05 16:23 (UTC) by Baerbeisser)

you will need to import the dev's signing key from GitHub

Ok, i find nothing on github.com/doitsujin/dxvk. How do i get the signing key? Do i need to generate it somehow?

Btw, afterwards pacman-key --recv-keys <key> is correct, yes?

eclairevoyant commented on 2023-01-31 04:48 (UTC) (edited on 2023-01-31 04:48 (UTC) by eclairevoyant)

Renaming a source is unnecessary here, especially in the last case where you're renaming the source to itself which makes no sense. But thanks for catching the missing modules.

HurricanePootis commented on 2023-01-31 00:30 (UTC)

Hey, you're not git cloning all of the git modules listed in .gitmodules within the PKGBUILD.

Here is a patch file to fix that

diff --git a/PKGBUILD b/PKGBUILD
index a101821..d8faedb 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,8 +14,12 @@ makedepends=(git gcc meson glslang)
 provides=(libdxvk libdxvk_dxgi.so libdxvk_d3d9.so libdxvk_d3d11.so)
 source=("git+$url.git?signed#tag=v$pkgver"
         "git+https://github.com/KhronosGroup/SPIRV-Headers.git"
-        "git+https://github.com/KhronosGroup/Vulkan-Headers.git")
+        "git+https://github.com/KhronosGroup/Vulkan-Headers.git"
+   "directx::git+https://github.com/Joshua-Ashton/mingw-directx-headers.git"
+   "libdisplay-info::git+https://gitlab.freedesktop.org/JoshuaAshton/libdisplay-info.git")
 b2sums=('SKIP'
+        'SKIP'
+        'SKIP'
         'SKIP'
         'SKIP')
 validpgpkeys=('273D040B5113B886D1A090D4C8CC613427A31C99') # Philip Rebohle <philip.rebohle@tu-dortmund.de>
@@ -25,6 +29,8 @@ prepare() {
    git submodule init
    git config submodule.include/spirv.url "$srcdir/SPIRV-Headers"
    git config submodule.include/vulkan.url "$srcdir/Vulkan-Headers"
+   git config submodule.include/native/directx.url "$srcdir/directx"
+   git config submodule.subprojects/libdisplay-info.url "$srcdir/libdisplay-info"
    git -c protocol.file.allow=always submodule update
 }

eclairevoyant commented on 2023-01-29 02:30 (UTC)

Adopted and updated. From this point on rather than using tarred releases, I will use the signed release tags (as per guidelines), which allows for PGP signature verification. Therefore, you will need to import the dev's signing key from GitHub or a keyserver (e.g. https://keyserver.ubuntu.com/).