This patch adds a port for Weston, now in version 2.0 and a GID for 'weston-launch'.
Weston is a reference implementation of a compositor using the Wayland protocol and libraries.
johalun0_gmail.com on May 4 2017, 12:49 PM.Authored by
Unfortunately the differential is without full context so I cannot inline the comments pertaining to graphics/wayland/Makefile.
Does wayland need WITH_DEBUG=1, or could that be an option or removed entirely?
The space after LIB_DEPENDS should be replaced by a tab to maintain proper alignment.
After fixing the two little bits I mentioned earlier, this new port builds on 10.3 x64, can be installed, and can run as a standalone Wayland compositor inside X11. A Wayland hello-world can connect and display things. After building qt5-wayland, Qt applications can use -platform wayland to display to the Weston window in X11 as well.
So from the perspective of running-in-X11, this is fine for kde@ as well. Excellent, in fact. Strongly desired.
I'm working on getting weston into the tree, just chasing some details now. I chased the libevent rename, I also cleanup the makefile a bit (mostly whitespace/location).
I want to put some info together which the user can use the get started, because I had to fight with XDG_RUNTIME_DIR before I could use weston-launch.
oh wow, I thought you abandoned this, and a few days ago I recreated the patch for weston git master :D
Anyway, consider using SHM_ANON in os_create_anonymous_file — with the current implementation, if XDG_RUNTIME_DIR is on ZFS (e.g. ~/.tmp), it will fail because posix_allocated is now unsupported on ZFS.
Thanks for the feedback. Will update the patch.
As an interested user, I wonder if using a group named 'weston-launch' is the best thing to do. My alternative thought would be to use something like 'wayland-launch', since there are two popular compositors today (weston and sway), and may be more in the future.
You could get into a situation where a Wayland app would be launchable under one compositor but not another.
I really wish I had available time to help with this effort. Thank you for pursuing this.
This has nothing to do with apps! 'weston-launch' is a group for users who are allowed to launch Weston itself using the 'weston-launch' setuid binary. That binary actually checks for that exact group name.
Greg, thanks for the clarification. I was under the impression (from a short-lived Wayland/(Weston || Sway) adventure about 1.5 years ago) that each app started its own compositor. Some discussion on the Sway github led me to believe that, IIRC.
Incidentally, that adventure took place on FreeBSD. It was rough, but I could run a graphic terminal under Weston (no X11), as well as the demo apps. Sway had some blocking Linux-isms I didn't have time to chase down. Super nice to see progress here.
But the "launch" stuff doesn't matter for any of that.
Has mesa gained option WAYLAND by default yet? I think that's what's blocking this, and (for instance) switching on Wayland in the KDE compositor (that is, KWin, which is one of the compositors which you can use to run a KDE desktop session or KDE applications).
Not yet, but it is on the way as far as I know.
Not only this. There is also absence of evdev in GENERIC kernel so in