That tutorial isnt very good as it has you dirty installing instead of making packages and assumes you only want the 64bit, you need both.
With newer mesa you only need add the --enable-nine flag in debian/rules . With pre 17.2 you need to add symbols from the error output of your first go and add d3dadapter.h and friends to libgl1-mesa-glx.install and mesa-common-dev.install. pbuilder takes care of the 32bit chroot stuff for you just remember to use ARCH=i386 AND --git-arch=i386 or the filenames dont work out right.
sudo apt-get install git-buildpackage
My biggest trouble with it was finding the right page to start reading, the page I found I already had:
file:///usr/share/doc/git-buildpackage/manual-html/gbp.intro.html
Good luck, and if you wait a week Iāll have a tutorial for ya but thatās basically itā¦ I had to upgrade to sid from buster to get 17.2 to compile with out frankendeb, libglvnd-core-dev isnt available in the 64bit repoās yet.
-M
Update: Think I may be wrong, you need to edit a few install files too, I had them already and forgot I did that
Ahh so Iām looking into this a bit more and I have a possible work around for you (need to rebuild again to test myself). Turns out even though theres been improvements to mesa weād basically have to rebuild QT at this point or work around it, and in our case we dont care really about the launchers graphics so:
export LIBGL_ALWAYS_SOFTWARE=1
./evelauncher.sh
and in your evelauncher, launch a script with:
export LIBGL_ALWAYS_SOFTWARE=0 before the wine command
So Iām trying the newer mesa out and having some odd issues (at bottom)ā¦ to stay on topic though, it would seem that infact gallium is software rendered but then how are we using dri? I donāt quite get the pipe I guess. Also Mesa 17.2 is working much slower for me but I probably have my own stupidity working against me there (no d3dadapter symbol diff in 17.2? no libGL?)
unset LIBGL_ALWAYS in the script makes my previous reply work as expected, with dx11, but infact dropping it from the script thus leaving it set 1 is what allowed me to use nine (if Iām using it right at all)
So, I type export LIBGL_ALWAYS_SOFTWARE=1 before ./evelauncher.sh and there is no more nouveau : push buf krec blablabla but
I donāt know how to launch a script inside the launcher. I have tried settings > use custom Wine and type āexport LIBGL_ALWAYS_SOFTWARE=1 wineā or export LIBGL_ALWAYS_SOFTWARE=1" in the field ācustom wine pathā
I have also tried āUse dev versionsā and type same commands in the winebug field.
But nothing happen when I click the āplayā buttonā¦
Here is my terminal output :
[0923/192740:WARNING:resource_bundle.cc(291)] locale_file_path.empty() for locale
Installed Qt WebEngine locales directory not found at location /home/.../evelauncher/translations/qtwebengine_locales. Trying application directory...
Qt WebEngine locales directory not found at location /home/.../evelauncher/qtwebengine_locales. Trying fallback directory... Translations MAY NOT not be correct.
[0923/192740:WARNING:resource_bundle.cc(291)] locale_file_path.empty() for locale
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.
English
Release
Run clients with logging
Run clients with dx9
Check use custom wine, and enter: /home/user/evelauncher/evelog.sh
My paths and prefix arent yours so change accordinglyā¦ hope that gets it for you!
M
P.S. cat ~/.local/share/CCP/EVE/Launcher/launcherlog-2017.09.23-13.44.37.135.txt
etc are generally the more useful logs, you can get to them through the pull down settings ā(E) -> show in file browserā as well.
