Might want to add:
if [ "$CC" = 'clang' ] && [ "$CXX" = 'clang++' ] || [ "$CC" = 'clang' ] || [ "$CXX" = 'clang++' ] ; then
export CC=gcc
export CXX=g++
export LD=ld
export AR=""
export NM=""
export RANLIB=""
export STRIP=""
export OBJCOPY=""
# Reset debug flags to makepkg.conf defaults, in case Clang is globally set
export DEBUG_CFLAGS="-g -fvar-tracking-assignments"
export DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"
fi
To make sure that, if a user has clang globally set, that it gets unset back to the Arch defaults to prevent builds from failing.
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.