Use NV_draw_buffers to implement EXT_draw_buffers

ui/gl/generate_bindings.py

Index: ui/gl/generate_bindings.py
diff --git a/ui/gl/generate_bindings.py b/ui/gl/generate_bindings.py
index 75f55c72e731e76ab6598940ecd496fd38755d83..10003afac49e018ee4ab8bacc9f0c2c3107d5cd7 100755
--- a/ui/gl/generate_bindings.py
+++ b/ui/gl/generate_bindings.py
@@ -216,7 +216,7 @@ GL_FUNCTIONS = [
   'names': ['glDrawBuffer'],
   'arguments': 'GLenum mode', },
 { 'return_type': 'void',
-  'names': ['glDrawBuffersARB', 'glDrawBuffersEXT'],
+  'names': ['glDrawBuffersARB', 'glDrawBuffersEXT', 'glDrawBuffers'],

[Zhenyao Mo, 2014/10/09 17:51:32]

I thought the NV extension function is glDrawBuffersNV? That's not defined in
any header files in chromium code base.  How does it magically map from
glDrawBuffersNV to glDrawBuffers?

[oetuaho-nv, 2014/10/10 07:42:15]

The intention is not to use glDrawBuffersNV, which has somewhat different
behavior, but to use glDrawBuffers from GLES3.0. NV_draw_buffers is used only to
enable ESSL 1.0 shaders to reference multiple render targets, the rest will work
according to GLES3.0 API, where DrawBuffers works the same way as in
EXT_draw_buffers.

Should I maybe add more explanation on this, maybe as a comment in
feature_info.cc?

   'arguments': 'GLsizei n, const GLenum* bufs', },
 { 'return_type': 'void',
   'names': ['glDrawElements'],