Skip to main content
Topic: wlroots (Read 192 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: wlroots

Reply #1
Code: [Select]
+        -Dlogind-provider=systemd \

Are you saying it should have said elogind?
anti-X  - artix - obarun - Void - systemD Free Space

I can no longer participate in a public forum side by side with neo-nazis and NSA trolls in a moderated sterile environment that is good for business.
Obviously the terms Open and Free mean nothing to you, or your business!



Re: wlroots

Reply #4
It honestly doesn't really matter anymore since elogind provides systemd now. Building with elogind or systemd activates exactly the same feature set (i.e. logind stuff).

Re: wlroots

Reply #5
It honestly doesn't really matter anymore since elogind provides systemd now. Building with elogind or systemd activates exactly the same feature set (i.e. logind stuff).
I wouldn't be too sure about that. sway currently says stuff about being unable to find backend for me, and apparently I'm not the only one
https://github.com/swaywm/sway/issues/4338
This is a user of an alternative init system having the same error as mine, and the options are to either use logind or set suid. They have a wiki page on this, and in the logind section (which they recommend), they say you should build wlroots with elogind explicitly or else it will expect libsystemd.
https://github.com/swaywm/sway/wiki/Running-Sway-without-systemd
Apparently for some things you can't just run it with systemd support and expect it to find your elogind. I have yet to try building it this way myself, but I'll report back with the results

Re: wlroots

Reply #6
I wouldn't be too sure about that. sway currently says stuff about being unable to find backend for me, and apparently I'm not the only one
https://github.com/swaywm/sway/issues/4338
This is a user of an alternative init system having the same error as mine, and the options are to either use logind or set suid. They have a wiki page on this, and in the logind section (which they recommend), they say you should build wlroots with elogind explicitly or else it will expect libsystemd.
https://github.com/swaywm/sway/wiki/Running-Sway-without-systemd
Apparently for some things you can't just run it with systemd support and expect it to find your elogind. I have yet to try building it this way myself, but I'll report back with the results

The guy in that issue was building sway+wlroots without any logind provider whatsoever. That works but you have to suid the binary. Here in Artix we just use wlroots built with logind support (i.e. using elogind) for simplicity and it's better security that way (as opposed to using suid but I'm sure some anti-logind folks will disagree with me there).

As far as the wiki page goes, it's technically a bit dated. elogind does provide systemd in pkgconfig since it is now totally compatible with the libsystemd api. When I originally added elogind support to wlroots, this wasn't the case. So you can actually just build wlroots without even having to specify any options assuming you have elogind installed. The default, libsystemd detection will work. Either way (elogind or systemd), there's no difference to wlroots. It activates exactly the same feature set (i.e. the logind backend). You can verify this real quick by looking at a couple of meson build files here and here.