User Tools

Site Tools


wiki:development:glx-xlib-workaround

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:development:glx-xlib-workaround [2020/08/20 20:58]
uli42
wiki:development:glx-xlib-workaround [2021/10/25 21:01] (current)
uli42 [Usage]
Line 28: Line 28:
 <code> <code>
 #!/bin/sh #!/bin/sh
-export LD_LIBRARY_PATH=<your directory>/libgl-xlib:${LD_LIBRARY_PATH} +LD_LIBRARY_PATH=<your directory>/libgl-xlib:${LD_LIBRARY_PATH} exec "$@"
-exec "$@"+
 </code> </code>
  
Line 35: Line 34:
 <code> <code>
 #!/bin/sh #!/bin/sh
-export LD_PRELOAD=<your directory>/libgl-xlib/libGL.so +LD_PRELOAD=<your directory>/libgl-xlib/libGL.so.1 exec "$@"
-exec "$@"+
 </code> </code>
  
Line 46: Line 44:
 </code> </code>
  
-Watch the output of the two glxinfo calls. You should see references to your mesa version and you should also see it reporting "GLX version: 1.4".+Watch the output of the two glxinfo calls. You should see references to your mesa version and you should also see it reporting "GLX version: 1.4", e.g. (shortened): 
 +<code> 
 +... 
 +server glx vendor string: Brian Paul 
 +server glx version string: 1.4 Mesa 18.0.5 
 +... 
 +client glx vendor string: Brian Paul 
 +client glx version string: 1.4 Mesa 18.0.5 
 +... 
 +GLX version: 1.4 
 +... 
 +OpenGL vendor string: VMware, Inc. 
 +OpenGL renderer string: llvmpipe (LLVM 3.8, 128 bits) 
 +OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5 
 +... 
 +</code> 
  
 Instead of creating the scripts mentioned above you can also add this to your .bashrc (or the config of your favourite shell): Instead of creating the scripts mentioned above you can also add this to your .bashrc (or the config of your favourite shell):
 <code> <code>
-export LD_LIBRARY_PATH=<your director>:${LD_LIBRARY_PATH}+export LD_LIBRARY_PATH=<your directory>/libgl-xlib:${LD_LIBRARY_PATH}
 </code> </code>
  
Line 56: Line 70:
 Now you can use one of these created wrapper scripts to run your application: ''x2goglx <your application>''. Some apps modify ''LD_LIBRARY_PATH'' so the ''x2goglx'' could have no effect. In that case try ''x2goglx2''. Now you can use one of these created wrapper scripts to run your application: ''x2goglx <your application>''. Some apps modify ''LD_LIBRARY_PATH'' so the ''x2goglx'' could have no effect. In that case try ''x2goglx2''.
  
-If you still cannot succeed you can try to find your if your application needs some special treatment. If so, please add the solution to the end of this page or post it to the mailinglist for some to add it.+If you still cannot succeedyou need to elaborate if your application needs some special treatment. If so, please add the solution to the end of this page or post it to the mailinglist for someone to add it here.
  
  
Line 132: Line 146:
 <code> <code>
 ebuild "/usr/portage/media-libs/mesa/mesa-${mesa_version}.ebuild" clean ebuild "/usr/portage/media-libs/mesa/mesa-${mesa_version}.ebuild" clean
 +</code>
 +
 +
 +===== NVidia driver / libGL =====
 +
 +On systems with a current (as of 2021) nvidia driver (including nvidia's libGL) instead of the above workaround you can try to run your application like this:
 +
 +<code>
 +__GLX_VENDOR_LIBRARY_NAME=mesa LIBGL_ALWAYS_SOFTWARE=1 <your application>
 </code> </code>
  
wiki/development/glx-xlib-workaround.1597957118.txt.gz · Last modified: 2020/08/20 20:58 by uli42