From: Thorsten Scherer <t.scherer@eckelmann.de>
To: ptxdist@pengutronix.de
Cc: Thorsten Scherer <t.scherer@eckelmann.de>
Subject: [ptxdist] [PATCH v2] libiio: Version bump 0.23 -> 0.25
Date: Tue, 10 Sep 2024 13:50:32 +0200 [thread overview]
Message-ID: <20240910115032.30832-1-t.scherer@eckelmann.de> (raw)
Bump version and drop iio_adi_xflow_check, which has been moved to the
examples folder, from LIBIIO_TEST_TOOLS.
Note from https://github.com/analogdevicesinc/libiio:
Since August 22th 2023, the "main" branch of libiio contains
what will eventually become libiio v1.0. It features a brand new API,
which is incompatible with libiio v0.25 and older. Have a look at the
wiki[1] for a description of the API changes.
[1] https://github.com/analogdevicesinc/libiio/wiki/libiio_0_to_1
Signed-off-by: Thorsten Scherer <t.scherer@eckelmann.de>
---
rules/libiio.make | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/rules/libiio.make b/rules/libiio.make
index 0cbc770044bf..ebd14b6ef777 100644
--- a/rules/libiio.make
+++ b/rules/libiio.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBIIO) += libiio
#
# Paths and names
#
-LIBIIO_VERSION := 0.23
-LIBIIO_MD5 := d23393bf1eefa0cd6fd4859efc453e95
+LIBIIO_VERSION := 0.25
+LIBIIO_MD5 := c8d5ea5ab44c2e99fab82baea9c92c57
LIBIIO := libiio-$(LIBIIO_VERSION)
LIBIIO_SUFFIX := tar.gz
LIBIIO_URL := https://github.com/analogdevicesinc/libiio/archive/v$(LIBIIO_VERSION).$(LIBIIO_SUFFIX)
@@ -67,7 +67,7 @@ $(STATEDIR)/libiio.targetinstall:
@$(call install_lib, libiio, 0, 0, 0644, libiio)
ifdef PTXCONF_LIBIIO_TEST_TOOLS
- @$(foreach testprog, adi_xflow_check attr genxml info readdev reg writedev, \
+ @$(foreach testprog, attr genxml info readdev reg writedev, \
$(call install_copy, libiio, 0, 0, 0755, -, \
/usr/bin/iio_$(testprog))$(ptx/nl))
endif
--
2.45.2
next reply other threads:[~2024-09-10 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 11:50 Thorsten Scherer [this message]
2024-09-16 14:34 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20240910115032.30832-1-t.scherer@eckelmann.de \
--to=t.scherer@eckelmann.de \
--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