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: 41
Popularity: 3.11
First Submitted: 2020-03-23 23:52 (UTC)
Last Updated: 2024-12-30 14:02 (UTC)

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 .. 24 25 26 27 28 29 30 31 32 33 34 Next › Last »

PedroHLC commented on 2021-01-18 18:05 (UTC)

Yeah, I've updated the makepkg.conf, actually changed the file-overwrite behaviour with an file-append of just what I need to change. So the CFLAGS shall be kept with currents upstream's makepkg.conf.

loathingkernel commented on 2021-01-18 18:02 (UTC)

@PedroHLC, correct me if I am mistaken, but you are building proton packages for redistribution through the chaotic-aur, correct? If so, I think we should find a way to build it with the proper CFLAGS from upstream, otherwise these packages might be under-performing if built targeting base x86_64.

PedroHLC commented on 2021-01-18 17:00 (UTC)

@loathingkernel, yeah you're right, was using an outdated makepkg.conf

PS: We got a stable 6.0 release now: https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.0-GE-1

loathingkernel commented on 2021-01-17 20:03 (UTC) (edited on 2021-01-17 20:03 (UTC) by loathingkernel)

Those flags is filtered for dxvk and vkd3d already, even if one was set, they wouldn't fail. Can you verify that any of those are not set for you chroot by mistake or omission?

PedroHLC commented on 2021-01-17 19:57 (UTC)

Clean chroot each build, so it shouldn't... And that's happening in winedbg functions not dxvk or vkd3d.

loathingkernel commented on 2021-01-17 19:54 (UTC) (edited on 2021-01-17 19:56 (UTC) by loathingkernel)

@PedroHLC, it shouldn't be broken, no. Are you building with -fstack-protector?

PedroHLC commented on 2021-01-17 19:16 (UTC) (edited on 2021-01-17 19:17 (UTC) by PedroHLC)

Is this broken with current mingw-w64? I tried building this and bumping to current git and both fail with a bunch of undefined reference to '__stack_chk_guard' and __stack_chk_fail. There is nothing in arch's bugzilla...

loathingkernel commented on 2020-12-08 10:13 (UTC) (edited on 2020-12-08 10:14 (UTC) by loathingkernel)

@juxuanu Thanks for the log. Well, as far as I can see, courier.ttf the build requires at that point is part of wine, and provided with the source, so I can't imagine what might be going on. It builds fine here, although I am not building in a chroot due to space constraints. If you are building on tmpfs, could it be that tmpfs fails silently due to not enough space? I really don't know yet, I am sorry.

juxuanu commented on 2020-12-08 08:46 (UTC)

Here it is, @loathingkernel. https://mega.nz/file/nJ0THSzL#YttG886Cz2pUQCNAoOnrugf3coyCmTaoF23TeZHaxDY

loathingkernel commented on 2020-12-07 21:02 (UTC)

@juxuanu what leads up to that error? An error like that alone is not informative.

« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 Next › Last »