mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-11-17 15:03:25 +09:00
[Feature] (EGL): Wayland window surfaces, presented through wl_shm
A Wayland client's window is its own wl_surface, and what the compositor shows is the wl_buffer attached to it - but the pixels of a MobileGL frame are drawn where the backend is, on a split build in another process on another OS. So far a wl_egl_window was taken for an X11 window and its client-side address sent to the Android server (EGL_BAD_NATIVE_WINDOW at best), and under glvnd a Wayland display never reached this vendor at all. A window on a Wayland display - asked for as EGL_PLATFORM_WAYLAND, or a wl_display recognised by its first word being wl_display_interface - is now a window surface in the EGL state at the wl_egl_window's size with a pbuffer of that size behind it in the backend, whatever MOBILEGL_IPC_SURFACE says. At every swap the frame is read back out of the default framebuffer through this library's own glReadPixels (the application's read framebuffer, pack buffer and pack state put back as they were), its rows flipped and swizzled into a wl_shm buffer, and attached, damaged and committed on the application's wl_surface. Three buffers rotate on their release events, dispatched on an event queue of the surface's own. libwayland-client is loaded at run time, so neither the build nor the library depends on it. EGL_KHR_platform_wayland and EGL_EXT_platform_wayland are announced on Linux. Measured: glmark2-wayland runs its build scene at 13 FPS (400x300) and the window shows the frame under kwin. A window resize is not followed yet; the surface keeps its creation size.
This commit is contained in:
@@ -406,6 +406,7 @@ set(SOURCE_FILES
|
||||
|
||||
MobileGL/MG_Impl/EGLImpl/Exporting/GlvndVendor.cpp
|
||||
MobileGL/MG_Impl/EGLImpl/EGLImpl.cpp
|
||||
MobileGL/MG_Impl/EGLImpl/WaylandWindow.cpp
|
||||
|
||||
# @INSERTION_POINT:SOURCE_FILE_GLIMPL@ #
|
||||
MobileGL/MG_Impl/GLImpl/Sampler/Validators.cpp
|
||||
|
||||
Reference in New Issue
Block a user