Package Details: proton-ge-custom 2:GE.Proton9.22-1

Git Clone URL: https://aur.archlinux.org/proton-ge-custom.git (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: https://github.com/GloriousEggroll/proton-ge-custom
Keywords: dxvk proton steam valve vkd3d wine
Licenses: custom
Provides: proton
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 40
Popularity: 2.23
First Submitted: 2020-03-23 23:52 (UTC)
Last Updated: 2024-12-30 14:02 (UTC)

Dependencies (117)

Required by (7)

Sources (12)

Pinned Comments

loathingkernel commented on 2023-10-12 10:43 (UTC) (edited on 2023-10-12 10:45 (UTC) by loathingkernel)

@rekman, thank you for looking into CUDA issues, at least it gives me an idea on how to fix it. That being said, my position remains to build it in a clean chroot, away from the locally installed packages. It is not feasible for me to carry patches for the build systems of various subprojects in the long run.

By enabling the 0003-AUR-Remove-kaldi-openfst-vosk-api-modules-because-of patch, you lose voice recognition which I assume is not that big of a loss as I haven't encountered a use for it, so I think it is an acceptable alternative.

patlefort commented on 2022-09-22 00:33 (UTC)

Compilation will fail if you happen to have jwasm installed, due to vulkan loader. Workaround: uninstall jwasm or add this line to prepape() in the PKGBUILD:

sed -i 's/VULKAN_LOADER_CMAKE_ARGS = -DUSE_MASM=OFF/VULKAN_LOADER_CMAKE_ARGS = -DUSE_MASM=OFF -DJWASM_FOUND=0/' "$srcdir/$pkgname/Makefile.in"

loathingkernel commented on 2020-11-21 10:28 (UTC) (edited on 2022-09-13 10:55 (UTC) by loathingkernel)

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 (Sniper, Soldier, etc) and as such it doesn't require it. Still, is detected by Steam and works properly (preferable through steam-native).

  • This PKGBUILD uses CFLAGS, CXXFLAGS and LDFLAGS hardcoded in the PKGBUILD itself. By default it uses the same C[XX]FLAGS as upstream, namely -march=nocona and -mtune=core-avx2. To change them you will have to edit the PKGBUILD itself. 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.

  • This package requires a Rust 32 bit target, please run rustup target install i686-unknown-linux-gnu BEFORE posting any issues if you're using rustup.

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 34 Next › Last »

patlefort commented on 2023-05-04 21:00 (UTC)

Fails for me too with same error, clean chroot and no march=native.

mihalycsaba commented on 2023-05-04 12:01 (UTC)

Build fails since yesterday big arch update, I'm using the -march=native flag

wineg++ -c -I/home/csaba/.cache/yay/proton-ge-custom/src/build/dst-wine64/include -Wno-attributes -ggdb -ffunction-sections -fdata-sections -fno-omit-frame-pointer -O2 -march=native -pipe -mno-avx2 -mfpmath=sse -fwrapv -fno-strict-aliasing -ffile-prefix-map=/home/csaba/.cache/yay/proton-ge-custom/src/build/src-steamexe=. -mcmodel=small -std=c++17  -I/home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include -I/home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/wine -I/home/csaba/.cache/yay/proton-ge-custom/src/build/dst-wine64/include/wine -I/home/csaba/.cache/yay/proton-ge-custom/src/proton-ge-custom/lsteamclient/steamworks_sdk_142/ -I/home/csaba/.cache/yay/proton-ge-custom/src/proton-ge-custom/openvr/headers/   -o steam.o steam.cpp
In file included from /home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/rpc.h:59,
                 from /home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/windows.h:60,
                 from steam.cpp:37:
/home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/rpcasync.h:139:7: error: declaration of ‘_RPC_ASYNC_NOTIFICATION_INFO::<unnamed struct> _RPC_ASYNC_NOTIFICATION_INFO::HWND’ changes meaning of ‘HWND’ [-Wchanges-meaning]
  139 |     } HWND;
      |       ^~~~
/home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/rpcasync.h:137:9: note: used here to mean ‘typedef struct HWND__* HWND’
  137 |         HWND hWnd;
      |         ^~~~
In file included from /home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/windef.h:290,
                 from /home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/windows.h:38:
/home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/windef.h:333:16: note: declared here
  333 | DECLARE_HANDLE(HWND);
      |                ^~~~
/home/csaba/.cache/yay/proton-ge-custom/src/build/src-wine/include/winnt.h:608:65: note: in definition of macro ‘DECLARE_HANDLE’
  608 | #define DECLARE_HANDLE(a) typedef struct a##__ { int unused; } *a
      |                                                                 ^
winegcc: /home/csaba/.cache/yay/proton-ge-custom/src/wrappers/x86_64-pc-linux-gnu-g++ failed
make[2]: *** [Makefile:87: steam.o] Error 2
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/csaba/.cache/yay/proton-ge-custom/src/build/obj-steamexe64/steam.exe'
make[1]: *** [../proton-ge-custom/Makefile.in:540: /home/csaba/.cache/yay/proton-ge-custom/src/build/.steamexe-build64] Error 2
make[1]: Leaving directory '/home/csaba/.cache/yay/proton-ge-custom/src/build'
make: *** [../proton-ge-custom/Makefile.in:1310: dist] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: proton-ge-custom-exit status 4

loathingkernel commented on 2023-03-24 08:46 (UTC)

@Gigas002 That's a problem with yay. If the tag is misplaced, i.e. labeling the wrong commit which sometimes happens, there is not much choice in the matter.

yay and paru which exhibits the same behavior should just start trusting the package suffixes.

Gigas002 commented on 2023-03-24 06:08 (UTC)

It seems like using commit in source instead of tag triggers yay to think about this package as git. Can this change be reverted?

eclairevoyant commented on 2023-03-13 02:34 (UTC)

@Gigas002 AUR helpers are not official software and therefore not supported in the AUR. You'll have to ask elsewhere about that, sorry.

Gigas002 commented on 2023-03-13 02:30 (UTC)

For an unknown reason yay sees this package as git-package since 2:GE.Proton7.50-4 version

loathingkernel commented on 2023-03-07 08:46 (UTC)

@patlefort Good point, thanks for mentioning it. I did a pkgrel-less update to not force a rebuild.

patlefort commented on 2023-03-07 01:57 (UTC)

Since libdisplay-info used here is a fork, could you please give it a different name in the source? Otherwise it conflict with the original in my source cache and it's used by gamescope.

eclairevoyant commented on 2023-01-17 23:54 (UTC) (edited on 2023-01-18 00:16 (UTC) by eclairevoyant)

@patlefort or build in a clean chroot as all packages should be built.

@mjevans if you really want to use a helper, I suggest using one that supports building in a clean chroot like paru or aurutils (but they still require some setup beforehand, FYI). Or you can use makechrootpkg as that's the officially supported way. This package builds fine for me and I built it yesterday.

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 34 Next › Last »