-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
[Feature] Wayland Support #2306
Comments
upstream issue: probonopd/linuxdeployqt#189 |
Just for sake of completion, this is the error message I get on Nobara 40 trying to compile 1ce65e8, which is a Fedora based distribution:
|
Why not just use flatpak. Better anyway and you dont have to deal with @probonopd |
Flatpak support is tracked here: #698 (comment) |
@probonopd wrote:
What do you mean pardon.? Just look at this issues title. Your are blocking a very simple wayland fix for years. Even if it would not have any downsides for non wayland user (if you are for some not understandble reqson). (Dont tell me about the like 1mb size increase actually matters ... There are people like me that don't want and insecure system with legacy decades old x11 no one wants to maintain anymore. And still using long deprecated fuse2, which does not get patched anymore. |
I am not blocking any fixes in Wayland. I am just not adding anything Wayland specific to my own tools, because I am not running Wayland and hence cannot test nor support it. There are many different tools that can deploy applications in the AppImage format, there is no need to use mine if they don't satisfy your needs. |
linuxdeploy (different from linuxdeployqt) has a Qt plugin with Wayland support, it seems like it was added here. |
I can understand not wanting to do the work yourself, but not accepting a very simple pr is "blocking" for me. Lets don't play word pickery. But I dont care then, if flatpak support is on the roadmap. But lets stop discussing here on some random projects issue |
Feature Request
Implement Wayland support as when building or trying to run the binary release with Wayland support fails.
The text was updated successfully, but these errors were encountered: