Evas GL: Fix sync, wlbuffer and image egl ext functions
authorJean-Philippe Andre <jp.andre@samsung.com>
Thu, 16 Jul 2015 13:25:36 +0000 (22:25 +0900)
committerJean-Philippe Andre <jp.andre@samsung.com>
Fri, 17 Jul 2015 05:47:42 +0000 (14:47 +0900)
commit8942c0c29bc0f58c8821136c03b6cbff9b5b13c8
treee68d6f050e4059fb71ad9531a950b2eac83236cd
parent51b097c014c77c36f708d3371a42e2045e003ba2
Evas GL: Fix sync, wlbuffer and image egl ext functions

Before this patch, those EGL/EvasGL functions can not work
without a current context. But EGL does not require any
current context for those to work, or at least, this should
be left to the driver to decide.

Evas GL was only able to get a pointer to the display
if a context was current.

The display pointer should be infered from Evas_GL unless
we can find a current display. EGL does not require a
context to be current in most of these function calls.

This should bring evasgl a little bit closer to EGL in terms
of behaviour (those are EGL-only extensions, btw).

Thanks @spacegrapher for the quick review

@fix
src/lib/evas/canvas/evas_gl.c
src/lib/evas/include/evas_private.h
src/modules/evas/engines/gl_common/evas_gl_api_ext.c
src/modules/evas/engines/gl_common/evas_gl_core.c
src/modules/evas/engines/gl_common/evas_gl_core.h
src/modules/evas/engines/gl_common/evas_gl_core_private.h
src/modules/evas/engines/gl_generic/evas_engine.c
src/modules/evas/engines/software_generic/evas_engine.c