Repository navigation
Conversation
A GL guest's libGL presents through GLX, and Mesa's kopper -- the zink path that hands its frames to the Vulkan WSI instead of copying them through XShmPutImage -- lives in the GLX frontend and initialises against the server's GLX extension. With `-Dglx=false` there is no such extension: wine's X11 driver fakes one under __ANDROID__ (hence WINE_X11FORCEGLX in the app's environment), and a kopper client has nothing to bind to, so the only GL path that worked was the shm copy — whose frames never create a VkSurface and therefore never meet the ICD's swapchain, cap, generation or release notes. Measured on the build: 1132 GLX strings in the binary, glxdri2 compiled in. The headers this needs are not all in the termux prefix: it ships glxproto.h, glxtokens.h and GL/internal/dri_interface.h but not GL/gl.h, GL/glx.h or GL/glext.h, so the build otherwise fails inside glx/createcontext.c. The script now checks for all four and names the missing one. Server-side GLX does not force a client to use it: a client that keeps presenting through XShmPutImage still can, so the existing GL path is unchanged by this.
This was referenced Nov 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A GL guest's
libGLpresents through GLX, and Mesa's kopper — the zink path thathands frames to the Vulkan WSI instead of copying them through
XShmPutImage—lives in the GLX frontend and initialises against the server's GLX extension.
This tree was built with
-Dglx=false, so there is no such extension. Wine's X11driver papers over it under
__ANDROID__(henceWINE_X11FORCEGLXin the app'senvironment), but a kopper client has nothing to bind to. The only GL path that
worked was the shm copy, whose frames never create a
VkSurfaceKHR— so theynever meet the ICD shim's swapchain, acquire cap, generation or release notes. A
GL title was invisible to the whole present path.
Change
-Dglx=true. Server-side GLX does not force any client to use it: a client thatkeeps presenting through
XShmPutImagestill can, so the existing GL path isbehaviourally unchanged.
GLX needs the libGL headers, and the termux build prefix ships the protocol ones
(
glxproto.h,glxtokens.h,GL/internal/dri_interface.h) withoutGL/gl.h,GL/glx.horGL/glext.h— the build otherwise fails deep insideglx/createcontext.c. The script now checks for all four up front and names themissing file.
Measured
Build: 2 413 920 B, 1132 GLX strings in the binary,
glxdri2compiled in.End to end on Retroid Pocket Nova (Adreno 740), SteamWorld Dig 2 under gamescope,
after the matching GL stack landed on the gamescope side:
Needs the gamescope side of this to be useful — the payload has to carry the GL
stack that can reach a GLX server. Companion: GameNative/gamescope#41.
Verified on that device only; no other Android GPU has been tried.