Here's a question that I came up with while replacing glx.so/libGL.so
with more recent snapshots (Utah GLX for G400, CVS).
Do conformant implementations have dependencies between libGL and the
GLX (DRI) in the server that warrant additional versioning/version testing?
I thought that GLX spec version and GL spec version should address all
issues, but that is seemingly not true at the moment (Nvidia GLX/Mesa3,
revisions of Utah GLX).
Even if any such incompatibility is a bug: consider the following
- user installs libGL.so and glx.so but does not restart X
- user has stray libGL.so somewhere in the path
- rogue and old applications shipped with own libGL.so
- statically linked GLX in (Nvidia, non XFree86) X server
An error message indicating an incompatible combination is used is
preferable to random crashes (especially if these happen delayed,
eg. when exiting X). If this is just an issue for the next few months,
fine, we should probably not bother.
Is there any recommendable way a well behaved application could check
and compare GLX and GL implementation/DLL version?
b.
--
"Problem solving is hunting. It is savage pleasure,
and we are born to it." Thomas Harris, Silence of the Lambs
