From: "Funda Wang" <fundawang@yeah.net>
To: linux-bluetooth@vger.kernel.org
Subject: [Patch] support libical 4.0
Date: Mon, 11 May 2026 13:58:38 +0800 (CST) [thread overview]
Message-ID: <1445e90e.ded.19e159db7d2.Coremail.fundawang@yeah.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 264 bytes --]
Hello,
Since libical 4.0 [1], pkgconfig files of libical have been splitted into several files according to libraries. The libical pkgconfig check need to be tweaked to check libicalvcal. Patch attached.
Thanks.
[1]: https://github.com/libical/libical/pull/988
[-- Attachment #1.2: Type: text/html, Size: 285 bytes --]
[-- Attachment #2: bluez-5.86-support-ical-4.0.patch.txt --]
[-- Type: text/plain, Size: 778 bytes --]
From e5128e1124efa814d8c65b4797025b1a15c6b250 Mon Sep 17 00:00:00 2001
From: Funda Wang <fundawang@yeah.net>
Date: Mon, 11 May 2026 12:37:35 +0800
Subject: [PATCH] support libical 4.0
---
configure.ac | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 52de7d6..1cdd551 100644
--- a/configure.ac
+++ b/configure.ac
@@ -306,7 +306,9 @@ fi
AC_ARG_ENABLE(obex, AS_HELP_STRING([--disable-obex],
[disable OBEX profile support]), [enable_obex=${enableval}])
if (test "${enable_obex}" != "no"); then
- PKG_CHECK_MODULES(ICAL, libical)
+ PKG_CHECK_MODULES(ICAL, [libicalvcal >= 4.0.0], [],
+ [PKG_CHECK_MODULES(ICAL, [libical])]
+ )
fi
AM_CONDITIONAL(OBEX, test "${enable_obex}" != "no")
--
2.47.3
next reply other threads:[~2026-05-11 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 5:58 Funda Wang [this message]
2026-05-11 7:44 ` [Patch] support libical 4.0 Bastien Nocera
2026-05-11 7:54 ` bluez.test.bot
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=1445e90e.ded.19e159db7d2.Coremail.fundawang@yeah.net \
--to=fundawang@yeah.net \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.