Linux bluetooth development
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: [BlueZ v10 03/16] build: Add support for building with libical 4.x
Date: Tue,  5 May 2026 10:45:09 +0200	[thread overview]
Message-ID: <20260505085741.2497401-4-hadess@hadess.net> (raw)
In-Reply-To: <20260505085741.2497401-1-hadess@hadess.net>

Some functions were moved to libicalvcal, use that library if we're
building against libical 4.0 or newer.

See https://github.com/bluez/bluez/issues/2090
---
 meson.build       | 6 ++++++
 obexd/meson.build | 1 +
 2 files changed, 7 insertions(+)

diff --git a/meson.build b/meson.build
index d3c43d79141f..15508a868636 100644
--- a/meson.build
+++ b/meson.build
@@ -134,6 +134,12 @@ cups_dep = dependency('cups', required: get_option('cups'))
 jsonc_dep = dependency('json-c', version: '>= 0.13', required: get_option('mesh'))
 alsa_dep = dependency('alsa', required: get_option('midi'))
 ical_dep = dependency('libical', required: get_option('obex'))
+ical4_dep = dependency('libical', version: '>= 4.0', required: false)
+if ical_dep.found() and ical4_dep.found()
+  icalvcal_dep = dependency('libicalvcal', required: get_option('obex'))
+else
+  icalvcal_dep = dummy_dep
+endif
 readline_dep = dependency('readline',
   required: get_option('client').enabled() or
     get_option('mesh').enabled())
diff --git a/obexd/meson.build b/obexd/meson.build
index baddafcd8873..2270a10cb423 100644
--- a/obexd/meson.build
+++ b/obexd/meson.build
@@ -100,6 +100,7 @@ executable('obexd',
     libgdbus_internal_dep,
     libshared_glib_dep,
     ical_dep,
+    icalvcal_dep,
     dbus_dep,
     ebook_dep,
     edataserver_dep,
-- 
2.54.0


  parent reply	other threads:[~2026-05-05  8:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  8:45 [BlueZ v10 00/16] Add meson build system and HTML docs Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 01/16] build: Add meson wrap for libell Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 02/16] build: Add meson build system Bastien Nocera
2026-05-05  8:45 ` Bastien Nocera [this message]
2026-05-05  8:45 ` [BlueZ v10 04/16] build: Separate systemd and libsystemd dependencies Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 05/16] tools: Install gatttool if deprecated tools are enabled Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 06/16] tools: Install avinfo tool by default Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 07/16] emulator: Install the emulator if built Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 08/16] build: Add option to allow disabling bluetoothd Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 09/16] unit: Run test-bap tests concurrently Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 10/16] unit: Make gobex-transfer tests run concurrently Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 11/16] build: Only build profiles if the daemon is built Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 12/16] build: Only build gdbus library if there is a user Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 13/16] unit: Add integration tests Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 14/16] doc: Add HTML documentation Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 15/16] github: Add docs deployment Bastien Nocera
2026-05-05  8:45 ` [BlueZ v10 16/16] doc: Add introduction to GATT Bastien Nocera

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=20260505085741.2497401-4-hadess@hadess.net \
    --to=hadess@hadess.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox