It's a very minor thing, but WINELOADER should be set to $WINE so that commands like winecfg can successfully launch. Otherwise protontricks -c winecfg <appid> will give an error:
wine: failed to initialize: /home/vagrant/build-proton_4.2-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
This is because winecfg, regedit, wineboot etc are all identical shell scripts that contain the lines
# determine the app Winelib library name
appname=`basename "$0" .exe`.exe
# first try explicit WINELOADER
if [ -x "$WINELOADER" ]; then exec "$WINELOADER" "$appname" "$@"; fi
If WINELOADER is not set then the system wine will be used.
WINEDLLPATH should be set simply because the proton script does. It should point to the wine directory in the proton library paths e.g:
WINEDLLPATH=$HOME/.local/share/Steam/steamapps/common/Proton 4.2/dist/lib64/wine:$HOME/.local/share/Steam/steamapps/common/Proton 4.2/dist/lib/wine
It's a very minor thing, but
WINELOADERshould be set to$WINEso that commands likewinecfgcan successfully launch. Otherwiseprotontricks -c winecfg <appid>will give an error:wine: failed to initialize: /home/vagrant/build-proton_4.2-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directoryThis is because winecfg, regedit, wineboot etc are all identical shell scripts that contain the lines
If
WINELOADERis not set then the system wine will be used.Current workarounds are:
protontricks -c 'wine winecfg' <appid>protontricks -c 'WINELOADER="${WINE}" winecfg' <appid>WINEDLLPATHshould be set simply because the proton script does. It should point to the wine directory in the proton library paths e.g:WINEDLLPATH=$HOME/.local/share/Steam/steamapps/common/Proton 4.2/dist/lib64/wine:$HOME/.local/share/Steam/steamapps/common/Proton 4.2/dist/lib/wine