Some paths don't check the proper EGL extensions before using them.

More extension checks.

Why do some ext check get their own helper and not others? It's seems very arbitrary.

We should really only use helpers when using IsExtensionSupported is onerous or tricky, as with EGL_KHR_image support (provided by either EGL_KHR_image or EGL_KHR_image_base) and EGL_KHR_image_pixmap (either EGL_KHR_image or EGL_KHR_image_pixmap).

Also EGLLibrary used to not have the same extension checking machinery, and just had a few bits with explicit helper functions. Could go either way, really -- you could always flag EGL_KHR_image as present if the required component extensions are present whether it's actually reported or not in the string, too.

(In reply to Vladimir Vukicevic [:vlad] [:vladv] from comment #4) > Also EGLLibrary used to not have the same extension checking machinery, and > just had a few bits with explicit helper functions. Could go either way, > really -- you could always flag EGL_KHR_image as present if the required > component extensions are present whether it's actually reported or not in > the string, too. This is also possible, though a little tricky. Technically if it supports EGL_KHR_image but not EGL_KHR_image_base, it's nearly identical, save for the PRESERVE EGLImage creation option.

I necromanced this.