On Sat, Nov 27, 1999 at 01:17:06PM -0800, Bernd Kreimeier wrote:
> 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?
There shouldn't be any such dependencies for indirect rendering.
However, revving libGL and the server GL libraries independently on the
same machine is an extremely unsafe practice. In the direct rendering
case there are likely to be dependencies between them, and typically
apps will use direct contexts with a local server.
There should be versioning mechanisms in client and server
independent of (below) GLX to deal with this - AIUI the PI DRI already
has some such behavior.
> 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).
If you get some problem when client and server are on separate
machines, that's a bonafide bug on somebody's part. I don't know how you
could meaningfully compare "DLL versions" when the client and server
libraries come from two completely different development tracks, though.
Jon Leech
SGI
