[Mesa-dev] Understanding GLX_INDIRECT_RENDERING (libOSMesa fails to link due to gl_dispatch_stub*)
jeremyhu at apple.com
Tue Jun 7 12:08:45 PDT 2011
On Jun 7, 2011, at 2:13 PM, Brian Paul wrote:
>> Ok, I see what is happening. configs/darwin bitrotted and included the -lGL, but other configs have since removed that. It looks like I should just remove -lGL from OSMESA_LIB_DEPS in addition to the other changes that I've already sent for osmesa.c
>> It looks like -lGL is still done in default, beos, and aix ... so someone might want to update those as well...
> At one time, I had things set up so that one libGL.so contained both the GLX and OSMesa interfaces. An app could create a context of each time and freely switch between them with glX/OSMesa-MakeCurrent(). A while back this got changed so the OSMesa stuff lives in its own libOSMesa.so library.
> At first glance, I'd suggest just omitting all the OSMesa stuff on Darwin for now.
Ok, well after omitting -lGL from OSMESA_LIB_DEPS and including the stubs in osmesa.c (patch on mesa-dev for review), things seem to be working well.
Is that patch the correct fix? Has libOSMesa been failing to build correctly on other architectures as well? If not, how is it resolving those symbols (or do architectures usually build libOSMesa without GLX_INDIRECT_RENDERING)?
I'm confused about how to interpret the matrix of GLX_INDIRECT_RENDERING and GLX_DIRECT_RENDERING:
^^ libGL supports both direct and indirect rendering
^^ libGL supports only indirect rendering (?)
^^ libGL supports only direct rendering (?) ... This doesn't seem to be the case since the indirect-foo is always included in src/glx/*.[hc]
^^ not supported?
More information about the mesa-dev