Linux bluetooth development
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: [BlueZ v10 06/16] tools: Install avinfo tool by default
Date: Tue,  5 May 2026 10:45:12 +0200	[thread overview]
Message-ID: <20260505085741.2497401-7-hadess@hadess.net> (raw)
In-Reply-To: <20260505085741.2497401-1-hadess@hadess.net>

It's used for checking which audio codecs are supported by a Bluetooth
audio device, which is more useful now that PulseAudio/PipeWire support
alternative codecs like LDAC or aptX).

Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=1699680
---
 tools/meson.build | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/meson.build b/tools/meson.build
index 5f092e7e1b5c..1c2595a31f77 100644
--- a/tools/meson.build
+++ b/tools/meson.build
@@ -61,7 +61,6 @@ if udevlib_hid2hci_dep.found()
 endif
 
 tools_names = [
-  'avinfo',
   'avtest',
   'scotest',
   'hwdb',
@@ -82,6 +81,7 @@ tools_names = [
 ]
 
 inst_tools_names = [
+  'avinfo',
   'rctest',
   'l2test',
   'l2ping',
-- 
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 ` [BlueZ v10 03/16] build: Add support for building with libical 4.x Bastien Nocera
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 ` Bastien Nocera [this message]
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-7-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