Mathias Agopian 9429e9c8ad first step for fixing [2066786] EGL object lifetime management doesn't respect the EGL spec ... this change fixes the lifetime mgt of EGLSurface, EGLContext and EGLImageKHR in the EGL wrapper. EGLDisplay is still somewhat bogus and libagl's EGL is still incorrect. The idea of the change is that EGL objects are put in a list when created and removed when destroyed. Before each use, we first verify if the object is in the list and if so a reference is taken and kept for the scope of the whole EGL API being called, if not, an error is returned. Upon object destruction, the object is simply marked as "terminated" (this is not protected by a lock because it doesn't really matter). This flag is only used to deny access to the object by other APIs while it's still valid (for instance current or being used by another function in another thread). A reference is also removed and the object can then actually be destroyed when going out of scope.		2009-08-21 19:45:44 -07:00
..
include	this header file is not needed anymore	2009-07-14 14:50:44 -07:00
libagl	better error handling in EGL	2009-08-20 00:12:56 -07:00
libs	first step for fixing [2066786] EGL object lifetime management doesn't respect the EGL spec	2009-08-21 19:45:44 -07:00
tests	show that we need to glClear to be fast(er)	2009-08-11 20:50:20 -07:00
tools/glgen