-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
CMake: USE_WAYLAND_WSI doesn't allow disabling Wayland support #11536
Comments
BTW Wayland is considered "found" even if wayland-egl is missing, but that might be on purpose. Just mentioning it in case it's a bug in
|
Your change looks fine to me, feel free to make a pull request. That could very well be a bug in FindWayland.cmake. Feel free to also fix that if you like :) |
Had a quick look at And it seems to consider that All in all I'd say let's not fix what's not broken -- if some users start complaining about not being able to build because they had a partial wayland dev setup, it can be investigated further. |
This change means that USE_WAYLAND_WSI=ON no longer triggers a fatal error if Wayland libraries are missing though, it will just show a message and continue building without Wayand WSI support. Closes hrydgard#11536.
What happens?
Building PPSSPPSDL on Linux with Wayland installed but
USE_WAYLAND_WSI=OFF
still links against Wayland (if installed on the system). The option seems to be only used to force check that wayland support will be enabled here:ppsspp/CMakeLists.txt
Lines 149 to 151 in f81dd83
What should happen?
I'd want the option to define whether Wayland should be used or not, and not simply whether its absence is a fatal error.
As such I'd propose something like the following diff. Opening an issue for feedback instead of a PR for now, as the current behaviour might be intended - I'm just suggesting to change it.
What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.
Mageia 7 x86_64 (Linux), PPSSPP 1.7.2/master.
The text was updated successfully, but these errors were encountered: