Alright, I think we've gotten to the bottom of this in the email chain.
We really need a shim EGL platform to adapt EGL_KHR_mir_platform to EGL_KHR_android_platform. This adaptation should be done in the shim, not within the android client platform.
I'd prefer a shim-layer to be proposed instead of this, just on the basis of it having 2-step initialization, deferred errors from ErrorDriverInterpreter and introducing temporary confusion about MirRenderSurface (which sparked all that email discussion)
Alright, I think we've gotten to the bottom of this in the email chain.
We really need a shim EGL platform to adapt EGL_KHR_ mir_platform to EGL_KHR_ android_ platform. This adaptation should be done in the shim, not within the android client platform.
I'd prefer a shim-layer to be proposed instead of this, just on the basis of it having 2-step initialization, deferred errors from ErrorDriverInte rpreter and introducing temporary confusion about MirRenderSurface (which sparked all that email discussion)