Nicolai Haehnle wrote:
The real issue with an IHV-supplied libGL.so is mixing vendors' graphics
cards. As an OpenGL user (i.e. a developer of applications that link
against libGL), I regularly switch graphics cards around to make sure
things work with all the relevant major vendors. Having a vendor-supplied
libGL.so makes this unnecessarily difficult on the software side (add to
that the custom-installed header files that have ever so slightly different
semantics, and there is a whole lot of fun to be had).
Not to mention the use case with two graphics cards installed at the same
time, from different vendors. While the above problem is annoying but
acceptable, there's simply no reasonable way to use two graphics cards from
vendors that insist on their custom libGL.so. Having to hack around with
LD_LIBRARY_PATH and the likes is ridiculous.
Hear hear.
I have such a two card system, I want to upgrade _one_
of them (an unstable pci radeon that hangs the machine
while doing 3d) but my options are limited indeed. There
is no use installing some card if it comes with software that
that disables my one working card - that way i'd
still only have one working 3D card. :-(
Helge Hafting
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
