-
-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamically selecting between X11 and Wayland backend #686
Comments
@Vendicated I can't reproduce. |
Apologies for the late reply, I'm only now looking into this again Are you sure you're not just running the binary through XWayland? For me, when compiling with
When compiling without the tag and using Wayland, it will open in XWayland. Or, if you are not using XWayland, error with
glfw has a GLFW_PLATFORM hint you can set to explicitly pick wayland/x11, introduced by the above linked commit that adds automatic platform selection, but go-glfw doesn't seem to even have this code. Does that mean it hasn't updated its glfw files to have that commit? I tried to hardcode the values in my code ( Looking more at go-glfw source, it seems like X11 and Wayland are mutually exclusive:
So it seems this is something that needs to be fixed by go-glfw? I'm sorry if i'm missing anything. Help would be greatly appreciated |
Could you try with the latest code? |
Oh I missed that. I did a Anyway, I updated to latest main and it's still failing without XWayland. Do i have to pass any specific build tags?
(On a side note, Text is also really messed up but you might already be aware of this?) |
Ok, let me check this |
This comment was marked as off-topic.
This comment was marked as off-topic.
giu uses glfw v3.3. |
Using
--tags wayland
, it is possible to create a wayland binaryHowever, I haven't found a way to create one binary that will run on both x11 and wayland, dynamically selecting the correct backend.
Is there any good way to do so? It seems like go-glfw doesn't even let you specify both x11 and wayland tag at once
GLFW itself does seem to support this though, see glfw/glfw@56a4cb0
The text was updated successfully, but these errors were encountered: