1 BlueZ - Bluetooth protocol stack for Linux
2 ******************************************
4 Copyright (C) 2000-2001 Qualcomm Incorporated
5 Copyright (C) 2002-2003 Maxim Krasnyansky <maxk@qualcomm.com>
6 Copyright (C) 2002-2010 Marcel Holtmann <marcel@holtmann.org>
9 Compilation and installation
10 ============================
12 In order to compile Bluetooth utilities you need following software packages:
16 - udev library (optional)
17 - readline (command line clients)
19 On a debian based system, this can be done by running the following command:
20 sudo apt-get build-dep bluez
24 ./configure --prefix=/usr --mandir=/usr/share/man \
25 --sysconfdir=/etc --localstatedir=/var
27 Configure automatically searches for all required components and packages.
29 To compile and install run:
33 Embedded Linux library
34 ======================
36 In order to compile mesh support and test client utility the development
37 version of Embedded Linux library is required to be present. The development
38 repositories can be found here:
40 git://git.kernel.org/pub/scm/libs/ell/ell.git
41 https://kernel.googlesource.com/pub/scm/libs/ell/ell.git
43 The build systems requires that the Embedded Linux library source code
44 is available on the same top level directory as the source code:
54 It is not required to build or install Embedded Linux library. The build
55 will happen when building the binaries and it will then be linked internally.
57 When using --enable-external-ell build option, it is not required that the
58 Embedded Linux library source code is available in the top level directory.
60 When neither --enable-mesh nor --enable-btpclient is specified, then this
61 part is irrelevant and Embedded Linux library is not required.
64 Kernel Build Options (for Mesh)
65 ===============================
67 The Mesh daemon uses kernel provided crypto utilities to perform security
68 functions required of Bluetooth Mesh. Many standard distributions currently
69 enable all required crypto features, but a few notable distributions do
72 If Mesh Cryptography is not working, the following configuration options
73 may need to be enabled, and the kernel rebuilt.
75 1. A minimum of kernel version 4.9 or later is required
77 2. The kernel must at a minimum have the following .config options turned on:
79 CONFIG_CRYPTO_USER_API
80 CONFIG_CRYPTO_USER_API_AEAD
81 CONFIG_CRYPTO_USER_API_HASH
89 Configuration and options
90 =========================
92 For a working system, certain configuration options need to be enabled:
96 Enable installation of Bluetooth library
98 By default the Bluetooth library is no longer installed.
100 The user interfaces or command line utilities do not
101 require an installed Bluetooth library anymore. This
102 option is provided for legacy third party applications
103 that still depend on the library.
105 When the library installation is enabled, it is a good
106 idea to use a separate bluez-library or libbluetooth
111 Disable support for Bluetooth utilities
113 By default the Bluetooth utilities are built and also
114 installed. For production systems the tools are not
115 needed and this option allows to disable them to save
116 build time and disk space.
118 When the tools are selected, it is a good idea to
119 use a separate bluez-tools package for them.
123 Disable support for CUPS printer backend
125 By default the printer backend for CUPS is build and
126 also installed. For systems that do not require printing
127 over Bluetooth, this options allows to disable it.
129 When the CUPS backend is selected, it is a good idea to
130 use a separate bluez-cups package for it.
134 Disable support for the Bluetooth monitor utility
136 By default the monitor utility is enabled. It provides
137 support for HCI level tracing and debugging. For systems
138 that don't require any kind of tracing or debugging
139 capabilities, this options allows to disable it.
141 The monitor utility should be placed in the main package
142 along with the daemons. It is universally useful.
146 Disable support for the command line client
148 By default the command line client is enabled and uses the
149 readline library. For specific systems where BlueZ is
150 configured by other means, the command line client can be
151 disabled and the dependency on readline is removed.
153 The client should be placed in the main package along
154 with the daemons. It is universally useful.
158 Disable integration with systemd
160 By default the integration with systemd is enabled and
161 installed. This gives the best integration into all
162 distributions based on systemd.
164 This option is provided for distributions that do not
165 support systemd. In that case all integration with the
166 init system is up to the package.
172 By default tools used only for testing emulation are disabled.
173 This option can be used to enable them.
175 It is not recommended to enable this option for production
176 systems. These tools may contain tests that depend on specific
177 environment or kernel features in development.
179 --enable-experimental
181 Enable experimental tools
183 By default all tools that are still in development
184 are disabled. This option can be used to enable them.
186 It is not recommended to enable this option for production
187 systems. The behavior of the experimental tools is unstable
188 and might still change.
192 This option enable NFC pairing support.
194 By default the integration with neard is disabled, this gives
195 the option to enable it in system where neard is supported.
197 The plugin is built into bluetoothd therefore it does not need
198 to be package separately.
202 This option enable SAP profile using sap plugin.
204 By default sap plugin is disabled since it requires tight
205 integration with systems and is very rarely required.
207 The plugin is built into bluetoothd therefore it does not need
208 to be package separately.
214 By default bluetoothd supports A2DP profile using a built-in
215 plugin, this option disables it.
217 This option is provided for distributions that do not have any
222 Disable AVRCP profile
224 By default bluetoothd supports AVRCP profile using a built-in
225 plugin, this option disables it.
227 This option is provided for distributions that do not have any
232 Disable PANU, NAP, GN profiles
234 By default bluetoothd supports PANU, NAP and GN profile using a
235 built-in plugin, this option disables it.
237 This option is provided for distributions that do not have any
238 network capabilities.
244 By default bluetoothd supports HID profile using a built-in
245 plugin, this option disables it.
247 This option is provided for distributions that do not have any
252 This option enable health profiles.
254 By default health plugin is disabled since its profiles are
255 target for the health industry.
257 The plugin is built into bluetoothd therefore it does not need
258 to be package separately.
262 This option enable MIDI support via ALSA Sequencer.
264 By default midi plugin is disabled since it still considered
265 experimental. When bluetoothd will create a new ALSA Sequencer
266 client and port for each device connected that supports the
267 MIDI GATT primary service.
269 The plugin is built into bluetoothd therefore it does not need
270 to be package separately.
276 linux-bluetooth@vger.kernel.org
278 For additional information about the project visit BlueZ web site: