Ian Romanick wrote:
Brian Paul wrote:
Ian Romanick wrote:
An issue was recently found with some extensions that are part of the
OpenGL core that are not exported by the indirect path. By exported
I mean that they are not listed by GL_EXTENSIONS. This caused at
least on hic-up when trying to test UT2k3 with
'LIBGL_ALWAYS_INDIRECT=y'.
I realize that there is no requirement to list EXT or vendor
extensions in GL_EXTENSIONS that are part of the core spec. However,
there are enough apps out there that do funky stuff that we probably
should.
My question is, how do we change the list of extensions exported by
the indirect path? I tried to figure it out about 8 months ago, but
I couldn't get the list of extensions to change.
New extensions require support in three places:
1. The server's renderer (s/w Mesa)
2. The server's GLX decoder
3. libGL's GLX encoder
libGL reports the intersection of the GL_EXTENSIONS strings for those
three components.
I don't know which extensions you're talking about, but most likely, 2
and 3 need to be updated. For extensions that just add new enums,
that's usually pretty easy. If you're adding new functions, that's
more work, but not too bad.
Heh...I just need to enable a few extensions like GL_EXT_bgra that are
already part of the core spec. UT2k3 (and I'm sure other applications
too) only check for the extension string and not for the core version.
Since these extensions are already part of the core spec that the
indirect path supports, there shouldn't be any encoder / decoder changes
necessary, should there?
correct.
-Brian
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
