X2Go - everywhere@home

User Tools

Site Tools

Trace:
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
Next revision Both sides next revision
wiki:development:glx-xlib-workaround [2017/11/04 11:28]
ionic Do not record development tools in world file if not strictly necessary. 		wiki:development:glx-xlib-workaround [2020/01/23 18:22]
uli42 [Approach]
Line 10: Line 10:
  
 Use a wrapper/proxy library provided by Mesa. The applications will use the supplied libGL.so, which in turn uses the lib interface to talk to the X server (nxagent) rather than the GLX interface. From the applications' perspective, they have GLX 1.4. Use a wrapper/proxy library provided by Mesa. The applications will use the supplied libGL.so, which in turn uses the lib interface to talk to the X server (nxagent) rather than the GLX interface. From the applications' perspective, they have GLX 1.4.
 +
 +Please note: the instructions below are not current anymore since mesa now mainly uses meson for building, athough still offerings scons. Please consult https://mesa3d.org/llvmpipe.html for a description how to compile the required library. Note that those instructions are incomplete as of Mesa 19.3.2, you need to call meson with some further parameters:
 +<code>
 +$ meson -D glx=gallium-xlib -D gallium-drivers=swrast -D platforms=x11 -D dri3=false -D dri-drivers="" -D vulkan-drivers="" -D buildtype=release -D optimization=3
 +$ ninja
 +</code>
  
 ==== Ubuntu 14.04 ==== ==== Ubuntu 14.04 ====
Line 37: Line 43:
 mkdir -p /usr/local/share/mesa-libgl-xlib mkdir -p /usr/local/share/mesa-libgl-xlib
 </code> </code>
 +
 Place the following line in a suitable place - either in your .bashrc or in the script that calls the individual application: Place the following line in a suitable place - either in your .bashrc or in the script that calls the individual application:
 <code> <code>
Line 42: Line 49:
 </code> </code>
  
-Configure portage to keep the working area that is used to compile the Mesa package. Before doing so, ensure that the USE flags for media-libs/mesa are configured to your liking.+Configure portage to extract and patch the Mesa package into a known location. Before doing so, ensure that the USE flags for media-libs/mesa are configured to your liking.
  
 <code> <code>
-export MESA_VERSION=$(equery -q list media-libs/mesa -F '$version') +mesa_version="$(equery -q list media-libs/mesa -F '$version')" 
-ebuild "/usr/portage/media-libs/mesa/mesa-${MESA_VERSION}.ebuild" prepare+ebuild "/usr/portage/media-libs/mesa/mesa-${mesa_version}.ebuild" prepare
 </code> </code>
  
 Now compile the library and move it over to the storage location: Now compile the library and move it over to the storage location:
 <code> <code>
-cd /var/tmp/portage/media-libs/mesa-${MESA_VERSION}/work/mesa-${MESA_VERSION}+cd "/var/tmp/portage/media-libs/mesa-${mesa_version}/work/mesa-${mesa_version}"
 scons libgl-xlib scons libgl-xlib
-cp build/linux-x86_64-debug/gallium/targets/libgl-xlib/* /usr/local/share/mesa-libgl-xlib/+cp -av build/linux-x86_64-debug/gallium/targets/libgl-xlib/* /usr/local/share/mesa-libgl-xlib/
 </code> </code>
  
Line 59: Line 66:
  
 <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> </code>
wiki/development/glx-xlib-workaround.txt · Last modified: 2021/10/25 21:01 by uli42

Page Tools

Imprint & Legal Disclaimer - Data Protection & Privacy Statement
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
GNU Free Documentation License 1.3 Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki