Having problems building this, seems there is a naming problem, any ideas?
../wine-ge-custom/wine/dlls/d3d12/d3d12_main.c:346:10: error: ‘const struct vkd3d_application_info’ has no member named ‘api_version’; did you mean ‘engine_version’? 346 | .api_version = VKD3D_API_VERSION_1_2, | ^~~~~~~~~~~ | engine_version ../wine-ge-custom/wine/dlls/d3d12/d3d12_main.c:346:24: error: ‘VKD3D_API_VERSION_1_2’ undeclared (first use in this function); did you mean ‘VK_API_VERSION_1_2’? 346 | .api_version = VKD3D_API_VERSION_1_2, | ^~~~~~~~~~~~~~~~~~~~~ | VK_API_VERSION_1_2 ../wine-ge-custom/wine/dlls/d3d12/d3d12_main.c:346:24: note: each undeclared identifier is reported only once for each function it appears in make: *** [Makefile:29593: dlls/d3d12/d3d12_main.o] Error 1 ==> ERROR: A failure occurred in build(). Aborting...
Pinned Comments
loathingkernel commented on 2022-03-02 14:12 (UTC)
@Strykar Nope, see https://aur.archlinux.org/packages/wine-ge-custom#comment-831304
You can grab compiled packages from https://github.com/loathingKernel/PKGBUILDs/releases/tag/packages
loathingkernel commented on 2021-10-15 10:01 (UTC) (edited on 2021-10-15 10:04 (UTC) by loathingkernel)
@thaewrapt, I see, you might be correct. The prebuilt package is not a good candidate for packaging for a couple of reasons. First of all, it is built using Lutris's runtime, and as such inherits the same issues as Proton, namely it is at its best when running inside that runtime. Also, although I might be wrong here, I haven't found any mention of Lutris being able to use a system-wide installation directory in the same way Steam can. For these reasons, I believe that packaging those binaries is pointless and they should be managed by Lutris itself.