Is there a clear way to compile KDE without Xwayland? Like, set some config option somewhere (hopefully, in one or two packages), and compile? Please?
No. Matter of fact in the near future x11 support will be completely gone.
I am pretty sure this does not apply to XWayland.
2 Likes
Is it irreversibly baked in? Why?
Unlikely.
Support for it could almost certainly be removed, or delegated to something like xwayland-satellite.
Just clarifying that the announcement to discontinue the Plasma X11 session support does not necessarily extend to XWayland
3 Likes
Lets clarify that x11 and x11 ARE two separate things and realistically have no bearing on one another. Xwayland is only available for programs that won’t convert or aren’t converted yet.
It’s doable, but why do you not want to even compile XWayland support?
If you do not want to use it, you can just not use it. Or change your kwin_wayland startup arguments not to include --xwayland.
I don’t think there’s even any KDE software other than KWin and window management libraries that might consume XWayland.
2 Likes
I can imagine a third possibility… portability and manpower reasons like in projects that also target and maintain other platforms or OS without a dedicated or sophisticated enough wayland implementation (yet) and go for the least common denominator which is probl. x11. (e.g. Opensolaris/Illumos, NetBSD… not sure about Haiku, Hurd).
The alternative would be to go for an abstraction layer, toolkit or some funky electron/webapp. But as always ymmv,
greetings from Plasma6, Wayland, FreeBSD
Does the KWIN_BUILD_X11 CMake option not work for you?
1 Like
Isn’t that compiled into the binary?
KWin has C++ code for handling X11/XWayland windows. Redstrate mentioned above that you can use the KWIN_BUILD_X11 CMake option to disable building that code.
XWayland itself is independent from KWin, so instead of building KWin without it, you can just… start a kwin_wayland instance without XWayland.
The first is about having support to start it, the second is about whether or not to start it. Doing the former might be overkill if all you want is the latter.
You still haven’t answered what you want to accomplish and for what reason.
1 Like
Well, I just want Xwayland :0 to not start at all. Right now, I start KDE via kwin_wayland, and it always spawns an instance of Xwayland :0. I try to kill Xwayland :0, and that crashes my DE. And I do not start kwin_wayland with any options, so I’m assuming Xwayland option is compiled in.
And when I run htop it shows kwin_wayland-wrapper with –xwayland option, but all that is baked into kwin binary.