Package Details: wine-ge-custom 1:GE.Proton8.26-2

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: 36
Popularity: 0.93
First Submitted: 2021-09-01 22:06 (UTC)
Last Updated: 2024-03-05 18:38 (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 12 Next › Last »

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?

loathingkernel commented on 2022-10-13 01:09 (UTC)

@bootlegbilly Refer here for the reasoning https://aur.archlinux.org/packages/proton-ge-custom

In short, feel free to try it, but I can neither filter nor test with any possible flags that might cause breakages. It is left as an exercise to the user.

bootlegbilly commented on 2022-10-12 13:47 (UTC)

How come the PKGBUILD overwites any custom CFLAGS? Is there a reason this can't be built with -march=native, -flto, or -O3?

subsurf commented on 2022-08-06 04:44 (UTC)

In addition to loathingkernel's PKGBUILDs on GitHub & ptr1337's repo, the Chaotic-AUR repo also provides automated compiled binaries for this package: https://aur.chaotic.cx/

ufo_driver commented on 2022-05-21 20:55 (UTC)

I just built mingw-w64-binutils with slightly changed official PKGBUILD and now building Wine with all $(nproc) CPUs :)

loathingkernel commented on 2022-05-10 13:59 (UTC) (edited on 2022-05-10 14:00 (UTC) by loathingkernel)

@dogunaut You are correct, this is an upstream mingw-w64-binutils issue. Personally I am 100% unequivocally against downgrading a package like that, especially forcing it through a dependency mandate to any unaware user. Users might want to do that themselves, but I can't endorse it in the PKGBUILD.

dogunaut commented on 2022-05-10 13:54 (UTC)

Issue seems to be caused by a bug in binutils. Unsure how bad of an idea it is, but downgrading my binutils to the previous version allows me to compile with max jobs again without any problems.

Bug & workaround found here: https://github.com/Frogging-Family/wine-tkg-git/issues/764

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