Package Details: wine-ge-custom 1:GE.Proton8.25-1

Git Clone URL: https://aur.archlinux.org/wine-ge-custom.git (read-only, click to copy)
Package Base: wine-ge-custom
Description: A compatibility layer for running Windows programs - GloriousEggroll branch
Upstream URL: https://github.com/GloriousEggroll/wine-ge-custom
Licenses: LGPL
Conflicts: wine
Provides: wine
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 35
Popularity: 1.53
First Submitted: 2021-09-01 22:06 (UTC)
Last Updated: 2023-12-02 12:26 (UTC)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

loathingkernel commented on 2023-05-24 22:15 (UTC) (edited on 2023-05-24 22:24 (UTC) by loathingkernel)

@Emilwojcik93 Your system has issues then, libfreetype.so should be discoverable by pkgconf.

Emilwojcik93 commented on 2023-05-24 21:32 (UTC) (edited on 2023-05-24 21:33 (UTC) by Emilwojcik93)

@loathingkernel I was able to build this package correctly by moddyfing two lines in PKGBUILD:

line 154

export PKG_CONFIG_PATH="/usr/lib/pkgconfig:/usr/share/pkgconfig:/usr/lib/libfreetype.so.6:/usr/lib/libfreetype.so"

line 179

export PKG_CONFIG_PATH="/usr/lib32/pkgconfig:/usr/share/pkgconfig:/usr/lib32/libfreetype.so.6:/usr/lib32/libfreetype.so"

loathingkernel commented on 2023-05-24 13:48 (UTC)

@Emilwojcik93 I don't know what you to tell you, freetype2 and lib32-freetype2 are in the depends array, they are in the Arch repos, and the package built fine the last time I built it.

Emilwojcik93 commented on 2023-05-24 13:04 (UTC) (edited on 2023-05-24 19:10 (UTC) by Emilwojcik93)

Similar problem like with wine-lol but idk how to resolve this:

configure: error: FreeType 64-bit development files not found. Fonts will not be built.
Use the --without-freetype option if you really want this.
==> ERROR: A failure occurred in build().
    Aborting...

sudo pacman -Qq | egrep "freetype"
egrep: warning: egrep is obsolescent; using grep -E
freetype2
lib32-freetype2

loathingkernel commented on 2023-04-04 17:16 (UTC) (edited on 2023-04-04 17:20 (UTC) by loathingkernel)

@begin-theadventu The reason I personally consider it a bad idea can be found in the pinned comments.

The reason why I didn't make a PKGBUILD repackaging the binary package in AUR is because such a package is useless to me.

begin-theadventu commented on 2023-04-04 15:28 (UTC)

What's the reason for the lack of a binary package, even though packages are built on GitHub?

Pook commented on 2023-02-15 00:05 (UTC)

@loathingkernel I'm happy with this package as a replacement for wine and wine staging. I use this package as my base wine and it takes precedence on my system.

loathingkernel commented on 2023-01-13 01:18 (UTC) (edited on 2023-01-13 01:18 (UTC) by loathingkernel)

@ewout

https://bugs.winehq.org/show_bug.cgi?id=45289

https://bugs.winehq.org/show_bug.cgi?id=43516

ewout commented on 2023-01-13 01:05 (UTC)

What's the reason AVX is disabled?

loathingkernel commented on 2022-10-31 11:47 (UTC)

Question towards anyone using this package, do you think it should be made to be install-able alongside regular wine or wine-staging from the repos but requiring some configuration overhead, or it is fine in the current state replacing those?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »