History log of /frameworks/base/core/jni/android_opengl_GLES10.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
9626f8203a8c222b8960a49cdc66d540fdb688b0 20-May-2014 Jesse Hall <jessehall@google.com> opengl: Fix #include style in generated JNI code

Bug: 15028495
Change-Id: Iad98380264c349fddf3b88df0c3a997d94c84fc8
01c26ea89d4bbea3cf550e9328742302dd9a2b25 24-Feb-2014 Ashok Bhat <ashok.bhat@arm.com> Use reinterpret_cast when an integer is cast to a pointer

Note that files changed in this patch have been generated
by running frameworks/native/opengl/tools/glgen/gen script.

Change-Id: Iff3ac2e804af41b9a6ec073fd65019c6806fe821
Signed-off-by: Ashok Bhat <ashok.bhat@arm.com>
cee5198e7199fcbb131ff0d30165fb1d5c0107cf 26-Apr-2013 Andy McFadden <fadden@android.com> Regenerate GL stubs

The primary motivation was to pick up changes to getarray(), but it
appears a few other tweaks were made since the last time the code
was generated.

Bug 8713753

Change-Id: I4fa2276bc28afaf0e1450e63498a8690028808ee
2ad0477f16c64dc3126741933f11e27353521bb4 23-Feb-2013 Mathias Agopian <mathias@google.com> regenerate GLES java bindings

- added most missing validation checks
- glGet* validation reimplement from khronos documentation

Bug: 7402895

Change-Id: I90528727e20480b5902d19bcb2dfbc6dc8b1367b
37c9b49ab5eb5a676370fd7081db0967c38e97a6 24-Jul-2012 Thomas Tafertshofer <tafertth@google.com> New bindings generated by glgen

Fixes crash of methods when NULL was used as a
(valid) parameter for a nio.buffer argument.

Bug: 6845189
Change-Id: Iae379d607bbca15d6d23e74e852f94c7f68637f9
17045a16575ece34cfadb63da4791f115625df78 12-Jul-2012 Thomas Tafertshofer <tafertth@google.com> Updated OpenGL bindings to fix nio buffer crash

Contains the updated OpenGL bindings generated by glgen.
Fixes a bug with methods that have more then one nio buffer argument.

Bug: 6772416
Change-Id: I6d50ce79669edd43dbe414e499660cdd55eb4893
2545b32ced69100fe70685b95315c6adf411083b 28-Jun-2012 Thomas Tafertshofer <tafertth@google.com> Fixed exception caused crash in GL bindings

Bug: 6709865
Change-Id: Iab55a9eda2ec686710872abf0ff2ebbdf382f77c
24ce5fb2cc09d0a14406e7b935f8648c5720d27e 09-Apr-2011 Elliott Hughes <enh@google.com> Kill the global references in the OpenGL wrappers.

Just use jniThrowException instead. Note that it would be trivial to throw
seemingly more appropriate exceptions (NullPointerException and
OutOfMemoryException in particular), but I'm only attempting to preserve
existing behavior here.

I also found shadowing bugs in some of the special-case functions, which
would previously always have leaked memory.

This also moves an accidental change to a generated file (ActivityThread ->
AppGlobals) into the generator, so it won't be overwritten in future.

Change-Id: Iab570310b568cb406c60dd0e2b8211f8a36ae590
16e7972f0d986eebf846ea8feb50f4435a9c6970 16-May-2009 Jack Palevich <jackpal@google.com> Fix bug 1856713 gl Pointer functions should use Buffer position

JSR239 and android.opengl gl Pointer functions (glColorPointer, etc.)
now respect the current setting of the Buffer position.

This fixes a regression introduced when we started requiring the
Buffers passed to the Pointer functions to be direct Buffers.
8331f72078051cdf5a26230ee819f7ef7f9fcc24 09-May-2009 Mathias Agopian <mathias@google.com> remove the gl{Vertex|Color|TexCoord|Normal}PointerBounds() "extension" fro eglext.h
e20ea783a12f1031482c3aa01938efe39dcbf0a2 08-May-2009 Jack Palevich <jackpal@google.com> Require native-order direct buffers for glXXXPointer APIs.

This was always a documented restriction, but was not enforced by the runtime until now.

Until now, if you passed in some other kind of buffer, it would sometimes work, and
sometimes fail. The failures happened when the Java VM moved the buffer data while
OpenGL was still holding a pointer to it.

Now we throw an exception rather than leaving the system in a potentially bad state.
be509c9c7de5929d014dfe6d45e71cc8454ede0f 07-May-2009 Jack Palevich <jackpal@google.com> Fix automatically generated code for glGet

Remove include of an internal agl header file. We should not depend on any implementation details
of our software renderer, since they may not be correct if another renderer is used.
Fix glGet number-of-elements logic for GL_FOG_COLOR GL_LIGHT_MODEL_AMBIENT,
a379585e6e3ff41db6d71a5cd0a0403931bc525d 24-Apr-2009 Jack Palevich <jackpal@google.com> Enable static Java APIs for OpenGL ES 1.1 extensions.

This is just plumbing. The Java APIs existed already, but there were no C APIs to hook the Java APIs
up to. Now there are C APIs, so we can call them.

Of course, whether or not the C APIs actually work when you call them depend upon the
capabilities of the active OpenGL driver, which must be checked at run time.

Also, while we're here, make the glGetString method static. It was always supposed to be static,
but was accidentally implemented as non-static, because the code was copied from the non-static
OpenGL ES classes.
27f8002e591b5c579f75b2580183b5d1c4219cd4 16-Apr-2009 Jack Palevich <jackpal@google.com> Add an Android-specific static OpenGL ES 1.1 Java API.

This change adds four new public classes that expose a static OpenGL ES 1.1 API:



+ The static API is slightly faster (1% to 4%) than the existing Interface based JSR239 API.
+ The static API is similar to the C API, which should make it easier to import C-based
example code.
+ The static API provides a clear path for adding new OpenGL ES 1.1 extensions
and OpenGL ES 2.0 APIs, neither of which currently have a JSR standard.


import static android.opengl.GLES10.*;



Note that it is possible to mix-and-match calls to both the static and JSR239 APIs.
This works because neither API maintains state. They both call through to the same underlying

Implementation details:

This change enhances the "glgen" "gen" script to generate both the original JSR239 and
new static OpenGL ES APIs. The contents of the generated JSR239 classes remained the same as before,
so there is no need to check in new versions of the generated JSR239 classes.

As part of this work the gen script was updated to be somewhat more robust, and to
work with git instead of perforce. The script prints out commands to git add the generated files,
but leaves it up to the script runner to actually execute those commands.