From: fundawang <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] d02777: build: Support libical 4.0
Date: Thu, 04 Jun 2026 04:25:02 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1105842/000000-d02777@github.com> (raw)
Branch: refs/heads/1105842
Home: https://github.com/bluez/bluez
Commit: d02777b690980cce8cc761b1ab040ba58e704c5e
https://github.com/bluez/bluez/commit/d02777b690980cce8cc761b1ab040ba58e704c5e
Author: Funda Wang <fundawang@yeah.net>
Date: 2026-06-04 (Thu, 04 Jun 2026)
Changed paths:
M configure.ac
Log Message:
-----------
build: Support libical 4.0
libical 4.0 split off some vcal related functions to a separate shared
library, libicalvcal. As libicalvcal depends on libical itself, first
check for libicalvcal being available, and if it fails, check for
just libical.
Closes: https://github.com/bluez/bluez/issues/2090
Tested-by: Bastien Nocera <hadess@hadess.net>
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-04 11:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1105842/000000-d02777@github.com \
--to=noreply@github.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox