mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libgpiod major version
Date: Wed, 20 Nov 2024 19:42:04 +0100	[thread overview]
Message-ID: <Zz4tfEXYK14ujQEO@lenoch> (raw)
In-Reply-To: <CAKd8=Gs9zB2mhsvySH8tE+gK8eL5u-0K5EC4eGZgp_pj2Di5rg@mail.gmail.com>

Hi,

On Tue, Nov 19, 2024 at 12:48:23PM +0100, Lars Pedersen wrote:
> Hi.
> 
> Libgpiod 2.+ has a lot of breaking changes, so should it be a separate
> package or should I just send a version bump on the existing one?

here it is as version bump. I'm using it for quite some time. It has no
in tree user...

From: Ladislav Michl <ladis@linux-mips.org>
Date: Mon, 22 Apr 2024 12:44:04 +0200
Subject: [PATCH] libgpiod: version bump 1.6.3 -> 2.1.1

This is a major release that breaks compatiblity with the v1.6.x series.
The entire data model has been overhauled in order to make using the
library more intuitive and less cumbersome, while also making the code
future-proof and extensible. Please refer to the documentation for
details.

Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
---
 rules/libgpiod.in   |  7 ++++---
 rules/libgpiod.make | 16 ++++++++++------
 2 files changed, 14 insertions(+), 9 deletions(-)

diff --git a/rules/libgpiod.in b/rules/libgpiod.in
index 14c38dddc..f18bed12e 100644
--- a/rules/libgpiod.in
+++ b/rules/libgpiod.in
@@ -44,12 +44,13 @@ config LIBGPIOD_GPIOSET
 	help
 	  Sets values of specified GPIO lines
 
-config LIBGPIOD_GPIOFIND
+config LIBGPIOD_GPIONOTIFY
 	bool
-	prompt "Install gpiofind"
+	prompt "Install gpionotify"
 	select LIBGPIOD_TOOLS
 	help
-	  Finds the gpiochip given the line name
+	  Wait for changes to info on GPIO lines and print them
+	  to standard output
 
 config LIBGPIOD_GPIOMON
 	bool
diff --git a/rules/libgpiod.make b/rules/libgpiod.make
index 937057cd7..fecc4db29 100644
--- a/rules/libgpiod.make
+++ b/rules/libgpiod.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBGPIOD) += libgpiod
 #
 # Paths and names
 #
-LIBGPIOD_VERSION	:= 1.6.3
-LIBGPIOD_MD5		:= 25b6d8e7ebda37bb9b55aa290af0f062
+LIBGPIOD_VERSION	:= 2.1.1
+LIBGPIOD_MD5		:= f3e8ab10da705d4b0f8c43e5c94beac9
 LIBGPIOD		:= libgpiod-$(LIBGPIOD_VERSION)
 LIBGPIOD_SUFFIX		:= tar.gz
 LIBGPIOD_URL		:= https://www.kernel.org/pub/software/libs/libgpiod/$(LIBGPIOD).$(LIBGPIOD_SUFFIX)
@@ -34,9 +34,13 @@ LIBGPIOD_CONF_TOOL	:= autoconf
 LIBGPIOD_CONF_OPT	:= \
 	$(CROSS_AUTOCONF_USR) \
 	--$(call ptx/endis, PTXCONF_LIBGPIOD_TOOLS)-tools \
+	--disable-gpioset-interactive \
 	--disable-tests \
+	--disable-profiling \
+	--disable-examples \
 	--$(call ptx/endis, PTXCONF_LIBGPIOD_CXX)-bindings-cxx \
-	--$(call ptx/endis, PTXCONF_LIBGPIOD_PYTHON3)-bindings-python
+	--$(call ptx/endis, PTXCONF_LIBGPIOD_PYTHON3)-bindings-python \
+	--disable-bindings-rust
 
 LIBGPIOD_CONF_ENV := \
 	$(CROSS_ENV) \
@@ -51,11 +55,11 @@ endif
 LIBGPIOD_LDFLAGS:= -Wl,-rpath-link,$(LIBGPIOD_DIR)/lib/.libs
 
 LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIODETECT)	+= gpiodetect
-LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIOINFO)	+= gpioinfo
 LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIOGET)	+= gpioget
-LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIOSET)	+= gpioset
-LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIOFIND)	+= gpiofind
+LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIOINFO)	+= gpioinfo
 LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIOMON)	+= gpiomon
+LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIONOTIFY)	+= gpionotify
+LIBGPIOD_TOOLS-$(PTXCONF_LIBGPIOD_GPIOSET)	+= gpioset
 
 # ----------------------------------------------------------------------------
 # Target-Install
-- 
2.39.5




      parent reply	other threads:[~2024-11-20 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 11:48 Lars Pedersen
2024-11-19 12:03 ` Markus Heidelberg
2024-11-22  7:35   ` Michael Olbrich
2024-11-20 18:42 ` Ladislav Michl [this message]

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=Zz4tfEXYK14ujQEO@lenoch \
    --to=oss-lists@triops.cz \
    --cc=ptxdist@pengutronix.de \
    /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