Package Details: proton-ge-custom 1:6.10.GE.1-3

Git Clone URL: (read-only, click to copy)
Package Base: proton-ge-custom
Description: Compatibility tool for Steam Play based on Wine and additional components. GloriousEggroll's custom build
Upstream URL:
Licenses: custom
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 9
Popularity: 1.59
First Submitted: 2020-03-23 23:52
Last Updated: 2021-06-10 18:56

Dependencies (184)

Required by (0)

Sources (30)

Pinned Comments

loathingkernel commented on 2020-11-21 10:28

Notes about this package

  • If you encounter issues while using this package, please contact me here first before reporting an issue to the upstream repository. Don't post logs, link to them. If you are using Manjaro, another derivative or an AUR helper, please mention it, I DO NOT TEST AGAINST THEM AND I CANNOT KNOW WHAT MIGHT BE WRONG WITH THE DISTRO/HELPER OF YOUR CHOICE.

  • It takes a LOT of time and space to build. Building with multiple jobs helps but might cause builds to fail in rare cases. Be sure to have at least 16GB of RAM if you are building on tmpfs

  • It is NOT built against steam linux runtime and as such it doesn't require it.

  • It hard-codes the CFLAGS and CXXFLAGS to be the same as upstream, if you want to change them, edit the PKGBUILD. Due to the nature of this package some flags can cause it to fail to build or not function properly. I try to filter them out but it is based on testing. If you have a feeling that compile-time options are involved in the issues you are having please include them in your comment. Currently the filtered options are -fstack-protector-{,-strong,-all}(dxvk and vkd3d only), -fno-plt, -z,relro, -z,now. Also the use of AVX instructions is disabled through -mno-avx.

  • If you are not using CFLAGS and CXXFLAGS specific to your system this package won't offer much in terms of performance as the upstream build flags already target the nocona (Core2) architecture. It will possibly perform worse than upstream. The only benefits you get is not depending on steam linux runtime as well as linking to Arch libraries. If you still want to build it, you can uncomment the relevant lines in the PKGBUILD to enable CFLAGS and CXXFLAGS similar to the upstream.

  • There have been reports with afdko failing to find its dependencies during building. I can't do anything about that as I don't maintain that package. It is NOT an issue with this package and I haven't found a way to not depend on it. Please don't report fails due to afdko (or any of its python- dependencies, they are pulled in due to afdko and only used by that), it has been discussed enough. There are possible workarounds in the comments.

  • It contains a patch to store game prefixes in the main Steam Library under $HOME/.local/share/Steam/steamapps/compatdata. It helps with isolation of game prefixes between users and works around issues with shared libraries on NTFS partitions due to drive symlinks. To enable it, set the PROTON_USER_COMPAT_DATA env variable to 1.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

loathingkernel commented on 2021-06-08 07:21

@markkuit yes, it would be absolutely fine to edit it out until you have pacman 6. I cannot comment on any other potential issues from reading the thread you linked.

markkuit commented on 2021-06-08 07:12

@loathingkernel thank you; for Manjaro users passing by, it looks like pacman is still at v5 due to ongoing pamac porting (see forum thread for more info).

Would it be safe (and working) to edit out the !lto option from the PKGBUILD when building, as a temporary fix for the time being?

loathingkernel commented on 2021-06-08 07:03

@markkuit yes, you are missing core/pacman 6.0.0-2

markkuit commented on 2021-06-08 06:39

With the addition of !lto in the options array in commit f304e64fbdfa ("Fix compilation error due to missing <optional> include"), this fails at the very beginning with: ==> ERROR: options array contains unknown option '!lto'.

This is on Manjaro, libalpm v12.0.2, Pacman v5.2.2, tried with Pamac 10.0.6-2 and yay v10.2.2. Am I missing something?

loathingkernel commented on 2021-06-07 17:25

@Nullrequest afdko should be installed by pip during the prepare step, I have confirmed this multiple times. Is there any special configuration around your system? Can you post a link to your build log?

randomguy343 commented on 2021-06-07 17:05

You need the afdko package.

Nullrequest commented on 2021-06-07 15:24

I am having a make issue where it fails with makeotf: command not found any idea why?

loathingkernel commented on 2021-06-03 16:14

The compile error should be fixed now.

Freso commented on 2021-06-02 19:31

Using Arch Linux, right after a fresh pacman -Syu, in a directory with a clean and fresh checkout of (ie., no altered C{,XX}FLAGS), running makepkg -fscCi results in this for me:

stdinUsrError commented on 2021-06-02 01:09

After installing lld and today's commit that fixed the issue with the dxvk repo I'm happy to report the AUR build completed successfully for me with pamac on Manjaro.

@loathingkernel Thanks for getting the issues sorted and maintaining this package!