From: Francesco Giancane <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] cac2ec: configure.ac: introduce `--enable-bluetoothd` flag
Date: Mon, 21 Jul 2025 08:36:33 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/984366/000000-3be9f5@github.com> (raw)
Branch: refs/heads/984366
Home: https://github.com/bluez/bluez
Commit: cac2ec3c4b77351a4be9d544c27484d986ed3e64
https://github.com/bluez/bluez/commit/cac2ec3c4b77351a4be9d544c27484d986ed3e64
Author: Francesco Giancane <quic_fgiancan@quicinc.com>
Date: 2025-07-21 (Mon, 21 Jul 2025)
Changed paths:
M configure.ac
Log Message:
-----------
configure.ac: introduce `--enable-bluetoothd` flag
Add an extra `configure.ac` flag to individually control `bluetoothd`
compilation.
Commit: b6ad18020b7586b84f64a5a3b0d797689ad466b0
https://github.com/bluez/bluez/commit/b6ad18020b7586b84f64a5a3b0d797689ad466b0
Author: Francesco Giancane <quic_fgiancan@quicinc.com>
Date: 2025-07-21 (Mon, 21 Jul 2025)
Changed paths:
M Makefile.am
Log Message:
-----------
Makefile.am: build `bluetoothd` if enabled
Keep daemon compilation and installation steps separated.
Commit: 3be9f5190a76edd3806281220030a5303cb446fb
https://github.com/bluez/bluez/commit/3be9f5190a76edd3806281220030a5303cb446fb
Author: Francesco Giancane <quic_fgiancan@quicinc.com>
Date: 2025-07-21 (Mon, 21 Jul 2025)
Changed paths:
M README
Log Message:
-----------
README: document `--enable-bluetoothd` flag
Document how to enable or disable compilation and installation of
the daemon `bluetoothd`.
Compare: https://github.com/bluez/bluez/compare/cac2ec3c4b77%5E...3be9f5190a76
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-21 15:36 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/984366/000000-3be9f5@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