• State Accepted Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 136 subscribers
  • Views 14110 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GL_OES_EGL_image_external with GLSL 3.0 shader and GLES 3.0 context?

Stephane Jacoby

Hello Mali driver devs,

It appears the GLSL 3.0 compiler doesn't support GL_OES_EGL_image_external extension, required by Android 3.0+ for use with SurfaceTexture. Recompilation for #version 100 instead of #version 300 es resolves the issue. GL_OES_EGL_image_external is present in the extension strings.

02-18 14:26:50.087: I/jbe(26539): Shader compile log:

02-18 14:26:50.087: I/jbe(26539): 0:32: P0003: Extension 'GL_OES_EGL_image_external' not supported

02-18 14:26:50.087: I/jbe(26539): 0:33: L0001: Typename expected, found 'samplerExternalOES'

Best regards,

Stephane

Parents
  • 0 in reply to Peter Harris

    Hi Pete,

    Makes sense. Indeed ES3 is not meant to be backwards compatible with ES2/1.1 extensions.

    Easy workaround for most, so no problem. Only caveat is that the resulting fragment shader compiled under #version 100 can only be linked with a vertex shader of the same GLSL #version.

    Best,

    Stephane

Reply
  • 0 in reply to Peter Harris

    Hi Pete,

    Makes sense. Indeed ES3 is not meant to be backwards compatible with ES2/1.1 extensions.

    Easy workaround for most, so no problem. Only caveat is that the resulting fragment shader compiled under #version 100 can only be linked with a vertex shader of the same GLSL #version.

    Best,

    Stephane

Children
No data