Skip to content

use GLFW's native XCB getters and drop the workaround library - #10

Draft
pknowles wants to merge 2 commits into
mainfrom
pknowles/glfw_native_xcb
Draft

pknowles wants to merge 2 commits into
mainfrom
pknowles/glfw_native_xcb

Conversation

@pknowles

Copy link
Copy Markdown
Owner

No description provided.

pknowlesnv and others added 2 commits September 24, 2026 22:16
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
GLFW_EXPOSE_NATIVE_XCB provides glfwGetXCBConnection/VisualID/Window
without including Xlib, so vulkan_objects_glfw_xcb and glfw_xcb_hack.cpp
are removed. vko::glfw:: keeps using-declarations for existing callers.

GLFW's getter returns NULL when X11-xcb is not loaded, e.g. with the
GLFW_X11_XCB_VULKAN_SURFACE init hint off. Presentation support now
checks it instead of passing NULL to the driver (llvmpipe segfaulted),
falling back to Xlib when enabled.

vulkan_objects no longer links X11/XCB libraries for XCB. Consumers that
call Xlib themselves must link it. The Xlib path now links X11::X11,
which it previously got from the XCB link. errorToString gains the error
codes added in GLFW 3.4.

Requires a GLFW with the XCB getters (glfw/glfw#2906). No release has
them yet, so VULKAN_OBJECTS_GLFW_TAG must be bumped once one does.
@pknowles
pknowles marked this pull request as draft September 25, 2026 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants