-
-
Notifications
You must be signed in to change notification settings - Fork 310
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
Wayland build: Could NOT find OpenGL (missing: GLX) #2019
Comments
If you are doing this on a headless system, maybe throwing 'xvfb-run --auto-servernum' before the command will allow it to work? I've never had to use that on cmake, but it usually helps with GLX errors on headless linux systems. Also, Is this node binaries that you are building? I'd check out the node workflow steps at Node needs the |
I remember seeing this old conversation that makes me think xvfb is needed with EGL on headless systems Btw, I just noticed you have a typo. the option is DMLN_WITH_EGL , not DMLN_WITH_ELG |
Thanks for the quick answer!
No, that's my main Desktop machine 🙈.
🤦♂️ you are right, and this one actually makes a difference, though it still gives an error for OpenGL (not sure if it fails earlier or later, though):
Let me see how far as go with that new error! |
I'd still give xvfb a try even if you aren't on a headless system. with non-egl node binaries, i have seen cases where the users video card driver does not support opengl, and gets opengl related errors. xvfb should allow it to emulate opengl if that was the case. |
Right, let me try. Also I am not building for node. I want to build C++ for Linux (so I'm running CMake from the root CMakeLists.txt, I assumed that was correct 🤔) and then for Android. I would like to contribute to Android, but I think I need to compile the C++ for that 👍. |
If you aren't building node I would assume you would just omit the I was thinking another thing you could try is if the opengl-2 branch behave differently. The opengl level has been raised in main, so maybe that branch would build differently? |
Hmm it seems like
They actually don't say much other than "use CMake" 🙈. Which is fine, it's probably just that I have an unusual system and I haven't found yet how to build for it. It feels like it should be possible given the other GitHub issues about Wayland.
Same issue there. Now I wonder if I need to install X11 compatibility stuff for Wayland, or if I am missing an option. I currently try with |
In the CMake module, it adds the
Because I set
And this fails to find
Feels like progress 🙈. |
I haven't read through entirely, but something to keep in mind is the wayland support is intended to be mutually exclusive with x11/xcb. Opposed to being additive. So you would need to disable all the x11/xcb support. I can take a look tomorrow |
I managed to pass the configure step with:
I really wonder if the CMakeLists should not set I worked around the last error (about the path to sleep.cc being wrong) by commenting out benchmarks (EDIT: my bad, it was a submodule issue). It is now building 🤞. |
I got it to build! I'll close this issue and will follow-up with a small PR meant to start a discussion about how the CMake configuration could be improved for Wayland. Thanks all for the help! |
I wonder if you add Edit: nevermind, i missed the comment |
Note: opening an issue here under the advice of @louwers on Slack, hoping to get insights from @jwinarske.
Trying to build maplibre-native on Wayland, I get the following error in the CMake configuration step:
I am running on Alpine 3.19 with Wayland.
I saw this issue and tried different things to remove the need for GLX (my understanding being that I don't need GLX on Wayland), like this:
But it does not change the GLX error I get. Am I missing something to build with Wayland?
The text was updated successfully, but these errors were encountered: