Package Details: lib32-gallium-nine-git 0.r167.4380a4c-1

Git Clone URL: https://aur.archlinux.org/gallium-nine-git.git (read-only)
Package Base: gallium-nine-git
Description: Gallium Nine Standalone (Git Version)
Upstream URL: https://github.com/iXit/wine-nine-standalone
Licenses: LGPL2
Conflicts: lib32-gallium-nine
Provides: lib32-gallium-nine
Submitter: jcstryker
Maintainer: jcstryker
Last Packager: jcstryker
Votes: 7
Popularity: 0.749597
First Submitted: 2019-01-07 21:49
Last Updated: 2019-02-22 12:20

Latest Comments

Xorg commented on 2019-05-25 15:09

@jcstryker: The official package, wine-nine, does not provide the nine-install script. This script is not needed when you install stuff under /usr/lib/wine.

You can see the difference of trees between the official package and yours here: https://gist.github.com/X0rg/50983aa0a3c32e6397157048ad100ad2

BTW, you should conflit and provide wine-nine. Also, your pkgver() function is wrong: git describe --long --tags | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g' is more adequate according to the wiki.

jcstryker commented on 2019-02-20 14:13

@zfkerr This package is not missing the install script, see line 72. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=gallium-nine-git#n72

zfkerr commented on 2019-02-20 08:44

@jcstryker your package is missing the /usr/share/nine/nine-install.sh file.

How can I install Nine-Standalone if this script is missing? I think you should add this script to your package. Thank you.

jcstryker commented on 2019-01-08 19:21

@PedroHLC @Nightbane112 Sorry about that, I included meson. Didn't have time to test in chroot, only on my workstation.

PedroHLC commented on 2019-01-08 18:00

@jcstryker I also need meson cause I'm building from clean-chroot, its automated and I can't interfere..

Nightbane112 commented on 2019-01-08 14:33

@jcstryker Is it possible to add meson to the makedepends in the PKGBUILD? I had build failures when using yay but I installed it later and it worked.

jcstryker commented on 2019-01-08 12:16

@kode54 Thanks!

@Senephar Yes you could, it has been possible to do this for a long time. This project is focused on building the d3d9 dll's separately from the wine tree, rather than packaging just the relevant dll's built from the iXit fork of wine. It also includes a symlinking script for easier install for multiple wine versions, not just separate prefixes e.g. proton and lutris wine builds. This PKGBUILD also splits the lib64/lib32 versions into separate packages, unlike wine-nine. I think both packages have their place.

Senephar commented on 2019-01-08 11:36

Why not just use wine-nine, which does the same but is build from the main nine repo, not some third party one?

https://aur.archlinux.org/packages/wine-nine/

kode54 commented on 2019-01-08 10:19

Here is a patch to get lib32-gallium-nine-git installed properly:

diff --git a/PKGBUILD b/PKGBUILD
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -45,8 +45,8 @@ build() {
       --cross-file "tools/cross-wine32" \
       --buildtype "release" \
       --prefix "/usr/share/nine" \
-       --bindir bin64 \
-      --libdir lib64 \
+       --bindir bin32 \
+      --libdir lib32 \
       "build32"

     ninja -C "build32"