README: add --enable-bindings-glib as required argument to build D-Bus
PATCH 1/1 README: add --enable-bindings-glib as required argument to build D-Bus
From: Bartosz Golaszewski <[email protected]>
GLib bindings to libgpiod are required to build D-Bus and both --enable-dbus and --enable-bindings-glib options must be passed to configure so make it clear in the README.
Suggested-by Douglas Silva <[email protected]>
Signed-off-by Bartosz Golaszewski <[email protected]>
--- README | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
README +5 -4
@@ -241,10 +241,11 @@ majority of the GPIO chardev's functionality and implement it from both the server and client sides in the form of the gpio-manager daemon and the gpiocli command-line utility for talking to the manager. -DBus support can be built by passing --enable-dbus to configure. The daemon -is bundled with a systemd unit file and an example configuration file for the -io.gpiod1 interface that allows all users to access basic information about the -GPIOs in the system but only root to request lines or change their values. +DBus support can be built by passing --enable-dbus and --enable-bindings-glib +to configure. The daemon is bundled with a systemd unit file and an example +configuration file for the io.gpiod1 interface that allows all users to access +basic information about the GPIOs in the system but only root to request lines +or change their values. With the manager running the user can run gpiocli to control GPIOs by asking gpio-manager to act on their behalf:
Signature · 1 line
2.43.0
Quoted 6 lines · Bartosz Golaszewski
From: Bartosz Golaszewski <[email protected]>
GLib bindings to libgpiod are required to build D-Bus and both --enable-dbus and --enable-bindings-glib options must be passed to configure so make it clear in the README.
I would prefer to have --enable-dbus automatically imply its --enable-bindings-glib dependency - you shouldn't have to pass multiple flags to build one thing.
Cheers,
Kent.