Zakhar Afonin

Wish this got more traction, this feature would be really useful for integrating glfw into existing projects using all the Windows-specific stuff on the window

0.5.0 produces a slightly different result: ``` Vsize: 24, 24 lib: /home/zaafonin/Downloads/Ninecraft/lib/x86/libminecraftpe.so: : 0x56742ce0 Ninecraft is running mcpe v0.5.0 4.6 (Compatibility Profile) Mesa 23.1.1 nine construct 0xd43bccc0 0xffdb46d0 debug: AppPlatform_linux::isPowerVR...

Done a GDB on ninecraft executable: ``` Thread 1 "ninecraft" received signal SIGSEGV, Segmentation fault. 0xf786a725 in _XSend (dpy=0x5667ec50, data=0x0, size=0) at /usr/src/debug/lib32-libx11/libX11-1.8.5/src/xcb_io.c:569 569 requests = dpy_request - dpy->xcb->last_flushed; (gdb)...

Attempted to swap the custom glfw for AUR's `lib32-glfw-wayland`. Surprisingly, a window actually does get initialized and loading gets quite far: ``` lib: /home/zaafonin/Downloads/Ninecraft/lib/x86/libminecraftpe.so: : 0x565f32e0 Ninecraft is running mcpe...

Commented out buffer swapping completely, and the game loads slightly further. On 0.6.1, *sometimes* (like 50% of times) the game crashes there: ``` Vsize: 24, 24 lib: /home/zaafonin/Downloads/Ninecraft/lib/x86/libminecraftpe.so: : 0x56676800...

Not the case. 32-bit Wine stuff wouldn't work either then.

Further observations. 1) The X11 segfault can be fixed by downgrading `lib32-libx11` to 1.6.8 (gosh that's ancient) 2) Segfaulting in libglvnd: ``` Thread 1 "ninecraft" received signal SIGSEGV, Segmentation fault....