<fdobridge>
<phomes_> testing zink/nvk using meson devenv should just work right? I build with -Dgallium-drivers=zink -Dvulkan-drivers=nouveau
<fdobridge>
<phomes_> I added some printfs to debug games on zink/nvk. But I do not seem to always hit them
<fdobridge>
<phomes_> if I launch a game directly from devenv then it is fine. But if I launch steam and then a game then it seems to use the system installed instead. If I use gamescope in the steam launch options then I do get the version from my devenv
<fdobridge>
<phomes_> I am so confused 🙂
<fdobridge>
<phomes_> I also tried using MESA_LOADER_DRIVER_OVERRIDE=zink in the steam launch options. Then I hit an error in zink - but again not the one from devenv.
<fdobridge>
<!DodoNVK (she) 🇱🇹> Maybe pressure-vessel is conflicting with devenv options? 🤷♀️
<fdobridge>
<phomes_> it would seem so. But how are people testing then? Do I have to do a system install to test?
<fdobridge>
<redsheep> That's what I've been doing
<fdobridge>
<Sid> yeah, pressure vessel is hardcoded to pull from the rootfs iirc
<fdobridge>
<zmike.> You probably need to set your LD_LIBRARY_PATH
<fdobridge>
<zmike.> @phomes_ this should be enough^
<austriancoder>
zmike: meson devenv does that already. I need to set VK_DRIVER_FILES to test zink/radv
<zmike>
yea that too
odrling has quit [Remote host closed the connection]
odrling has joined #zink
odrling has quit [Remote host closed the connection]
odrling has joined #zink
odrling has quit [Remote host closed the connection]
odrling has joined #zink
Low_Orbit_Michelson-Morley has quit []
<fdobridge>
<phomes_> meson devenv sets both LD_LIBRARY_PATH and VK_DRIVER_FILES