From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
Erik Schilling <erik.schilling@linaro.org>,
Phil Howard <phil@gadgetoid.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Philip Withnall <philip@tecnocode.co.uk>
Cc: linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Alexander Sverdlin <alexander.sverdlin@siemens.com>
Subject: [PATCH libgpiod v4 08/18] README: document GLib bindings
Date: Wed, 07 Aug 2024 11:10:39 +0200 [thread overview]
Message-ID: <20240807-dbus-v4-8-64ea80169e51@linaro.org> (raw)
In-Reply-To: <20240807-dbus-v4-0-64ea80169e51@linaro.org>
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Add information on the requirements of and the configure build switch
for GLib bindings to libgpiod.
Tested-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
README | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/README b/README
index a01cfc5..658a77e 100644
--- a/README
+++ b/README
@@ -211,13 +211,16 @@ Examples:
BINDINGS
--------
-High-level, object-oriented bindings for C++, python3 and Rust are provided.
-They can be enabled by passing --enable-bindings-cxx, --enable-bindings-python
-and --enable-bindings-rust arguments respectively to configure.
+High-level, object-oriented bindings for C++, GLib, python3 and Rust are
+provided. They can be enabled by passing --enable-bindings-cxx,
+--enable-bindings-glib, --enable-bindings-python and --enable-bindings-rust
+arguments respectively to configure.
C++ bindings require C++11 support and autoconf-archive collection if building
from git.
+GLib bindings requires GLib (as well as GObject, GIO and GIO-Unix) v2.54.
+
Python bindings require python3 support and libpython development files. Please
refer to bindings/python/README.md for more information.
--
2.43.0
next prev parent reply other threads:[~2024-08-07 9:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 9:10 [PATCH libgpiod v4 00/18] dbus: add GLib-based D-Bus daemon and command-line client Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 01/18] tests: split out reusable test code into a local static library Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 02/18] tests: split out the common test code for bash scripts Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 03/18] bindings: glib: add build files Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 04/18] bindings: glib: add public headers Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 05/18] bindings: glib: add core code Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 06/18] bindings: glib: add examples Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 07/18] bindings: glib: add tests Bartosz Golaszewski
2024-08-07 9:10 ` Bartosz Golaszewski [this message]
2024-08-07 9:10 ` [PATCH libgpiod v4 09/18] dbus: add build files Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 10/18] dbus: add the API definitions Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 11/18] dbus: add a wrapper around the gdbus-codegen generated header Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 12/18] dbus: add data files Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 13/18] dbus: add gpio-manager code Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 14/18] dbus: add tests Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 15/18] dbus: add a command-line client Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 16/18] dbus: client: add tests Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 17/18] README: document the DBus API Bartosz Golaszewski
2024-08-07 9:10 ` [PATCH libgpiod v4 18/18] TODO: drop the DBus daemon from the list Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240807-dbus-v4-8-64ea80169e51@linaro.org \
--to=brgl@bgdev.pl \
--cc=alexander.sverdlin@siemens.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=erik.schilling@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=phil@gadgetoid.com \
--cc=philip@tecnocode.co.uk \
--cc=viresh.kumar@linaro.org \
--cc=warthog618@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).