We have found lately an issue that the OGLBASE does not address
properly, but it's still an issue.
There are now some Linux distributions, which that put Mesa under the
name libGL.so.1.2.0 unter /usr/lib. This is so far ok. Now we (XiG) do
ship a 1.1 based libGL.so.1.1. The problem is now a installation
problem. If we simply copy our own library into /usr/lib, it will
never be used, because the naming of the Mesa based library implies
that it's newer, and will be used. So there are two ways of handling
that:
1. We ship of 1.2 based library, and simply call it libGL.so.1.2.0.
Doesn't really address the problem, as there will be a Mesa based
library called libGL.so.1.2.1, and the same old problem will be
there.
2. Simply remove the current exisiting libGL.so at installtime.
Well, this is subobtimal as well, as then if a user wants to go
back to the original version, then where to get the original
library from ?
The issue goes deeper with the include files in /usr/include/GL as
well. It's understood that gl.h and glx.h should be interchangeable,
but for simple support reasons it would be nice to install the ones
that came with the libGL.so (this might be a future OpenGL 1.3
vs. OpenGL 1.2 issue as well).
My question is how to handle those scenarios. The are really BIG
issues for everybody shipping a driver or a complete libGL.so, as
there are always versioning problems.
- Thomas
--
Thomas Roell /\ An imperfect plan executed violently
Xi Graphics / \/\ _ is far superior to a perfect plan.
[EMAIL PROTECTED] / / \ \
/ Oelch! \ \ George Patton
