-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/09/2011 11:53 PM, Chad Versace wrote:
> + { "GL_OES_framebuffer_object",
> o(ARB_framebuffer_object), ES1 },
I think this and the other OES framebuffer object related extensions
should depend on EX
On 01/10/2011 07:18 AM, Brian Paul wrote:
> Why not just defined the GL, ES1 and ES2 bits to be 1 << gl_api like this:
>
> GL = 1 << API_OPENGL
> ES1 = 1 << API_OPENGLES
> ES2 = 1 << API_OPENGLES2
>
> That'd make api_bit() trivial.
Ah, I've never seen that trick before: bit-shifing on enum value
On 01/10/2011 12:53 AM, Chad Versace wrote:
Place GL, GLES1, and GLES2 extensions in a unified extension table. This
allows one to enable, disable, and query the status of GLES1 and GLES2
extensions by name.
When tested on Intel Ironlake, this patch did not alter the extension
string [as given b
Place GL, GLES1, and GLES2 extensions in a unified extension table. This
allows one to enable, disable, and query the status of GLES1 and GLES2
extensions by name.
When tested on Intel Ironlake, this patch did not alter the extension
string [as given by glGetString(GL_EXTENSIONS)] for any API.
---
Place GL, GLES1, and GLES2 extensions in a unified extension table. This
allows one to enable, disable, and query the status of GLES1 and GLES2
extensions by name.
When tested on Intel Ironlake, this patch did not alter the extension
string [as given by glGetString(GL_EXTENSIONS)] for any API.
---
