[Xprint] SuSE and Mesa/GLX...

[Roland Mainz]

Hi!

----

Is there a specific reason why libGL.so on SuSE tries to tranfer giant
images over the wire when the remote Xserver supports the GLX extension
?

After some resarch I found that my problem is related to the issue that
SuSE uses "/usr/lib/GL/libGL.so.1.4.mesasoft" for "/usr/bin/libGL.so"
instead of "/usr/lib/GL/libGL.so.1.2.xf86_glx":
-- snip --
% ls -1 /usr/lib/GL/libGL.so.1.*
/usr/lib/GL/libGL.so.1.2.xf86_glx
/usr/lib/GL/libGL.so.1.4.mesasoft
-- snip --
This has two sideeffects:
1. Using GLX on SuSE on a remote framebuffer _always_ uses Mesa which is
bad, esp. when you have a Sun ZULU framebuffer (XVR-4000) on the other
end which is much faster than anything on the Linux side.
2. Printing using the OpenGL API via the Xprint server (which now
supports the GLX extension) results in transfers of _GIGANTIC_ images
instead if just the OpenGL rendering instructions.

Egbert:
Any idea how to solve that ?

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)