@class101
mingw-w64-tools
offerswidl
which is required to buildvkd3d-proton
, it is also offered by wine, butmingw-w64-tools
is smaller and is the proper tool.lib32-gsm
is the x86 counterpart ofgsm
and is required for equality between the x86 and x86_64 builds of wine.
Pinned Comments
loathingkernel commented on 2020-11-21 10:28
Notes about this package
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
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 toafdko
(or any of itspython-
dependencies, they are pulled in due toafdko
and only used by that), it has been discussed enough. There are possible workarounds in the comments.This PKGBUILD uses
CFLAGS
,CXXFLAGS
andLDFLAGS
frommakepkg.conf
. 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
.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 symlinks. To enable it, set thePROTON_USER_COMPAT_DATA
env variable to1
.It is NOT built against
steam linux runtime
and as such it doesn't require it.If you are not using
CFLAGS
andCXXFLAGS
specific to your system this package won't offer much in terms of performance as the upstream build flags already target thenocona
architecture. It will possibly perform worse than upstream. The only benefits you get is not depending onsteam linux runtime
as well as linking to Arch libraries.