On Sun, 9 Jun 2024 13:12:44 GMT, Thiago Milczarek Sayao <tsa...@openjdk.org> wrote:
>> Wayland implementation will require EGL. >> >> EGL works with Xorg as well. The idea is to be EGL first and if it fails, >> fallback to GLX. A force flag `prism.es2.forceGLX=true` is available. >> >> >> See: >> [Switching the Linux graphics stack from GLX to >> EGL](https://mozillagfx.wordpress.com/2021/10/30/switching-the-linux-graphics-stack-from-glx-to-egl/) >> [Prefer EGL to GLX for the GL support on >> X11](https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3540) > > Thiago Milczarek Sayao has updated the pull request with a new target base > due to a merge or a rebase. The pull request now contains ten commits: > > - Merge branch 'refs/heads/master' into egl > - Merge branch 'refs/heads/master' into egl > - Merge branch 'refs/heads/master' into egl > - Use prismES2EGLX11 as build name > - Merge branch 'master' into egl > - Prefer EGL over GLX > - Merge branch 'master' into egl > - Merge branch 'master' into egl > > # Conflicts: > # modules/javafx.graphics/src/main/native-prism-es2/x11/X11GLContext.c > - Use EGL instead of GLX Would it be better to still default to GLX and have a flag to use EGL (and switch within a few releases), or to go with EGL and have a flag to fallback to GLX? Currently (on this PR) it defaults to EGL first, and if it fails, try GLX (I don't know a scenario where EGL won't work, on Xorg o XWayland). ------------- PR Comment: https://git.openjdk.org/jfx/pull/1381#issuecomment-2214100176
