On 07-Sep-99 Brian Paul wrote:
>
> Here's another issue. There's an effort underway to standardize
> the OpenGL environment on Linux. One aspect of that is version
> numbering for the libGL.so file (used to be libMesaGL.so).
>
> I propose this lib name for the 3.1 release: libGL.so.1.2.310
> The 1.2 designates an implementation of the 1.2 API specification.
> The 310 designates the Mesa version number (3.1.0). The main idea
> is to allow Linux OpenGL apps to relink with other OpenGL
> implementations at load/runtime. Comments?
Two questions about this:
1) what group will be maintaining the GLU implementation? Will that stay with
core Mesa? If I recall, the glx-dev group (working on the g200/g400/nvidia/ati
drivers) does not build a glx library when you compile that setup, though you
have to have already downloaded Mesa so I guess it's not too much of an issue.
On the other hand, I think nvidia's reference implementation for linux *did*
include its own glu library -- are these the same? Should people continue to
look to Mesa for the de facto standard glu implementation?
2) What's the best way to handle multiple drivers for different chipsets? It
almost seems like it would make sense to have each of the Mesa versions be
named something to do with it's chipset -- ie libGx00GL.so.1.0,
libVoodooGL.so.1.0, libRivaGL.so.1.0, etc, and then automagically symlink that
file to libGL.so[.1[.0]] at compile/install time. I don't know a lot about the
way ld works on systems aside from linux -- but doesn't the linux ld internally
assign the root name of the library component? Could you set the internal
library name to libGL.so.1.0 and then the name-on-the-hard-drive to the
descriptive name, and then symlink around to make things work? Or is there a
better way to handle this?
On the one hand, I think this might become less and less of an issue as the
Voodoo/Voodoo2 cards age and are replaced with 2D/3D combo cards, but the
problem will probably pop up again -- isn't XF86 4 supposed to have multi-head
support? How do you determine which libGL is the right one for each display in
that case?
Joe
>
> -Brian
>
>
> _______________________________________________
> Mesa-dev maillist - [EMAIL PROTECTED]
> http://lists.mesa3d.org/mailman/listinfo/mesa-dev
--
Joe Waters ([EMAIL PROTECTED]) Aegis Simulation Technologies
Shoot stuff. Break things. Impress your friends.
We can help. Play BFRIS. http://www.aegistech.com
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
