1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
|
BlueZ - Bluetooth protocol stack for Linux
******************************************
Copyright (C) 2000-2001 Qualcomm Incorporated
Copyright (C) 2002-2003 Maxim Krasnyansky <maxk@qualcomm.com>
Copyright (C) 2002-2010 Marcel Holtmann <marcel@holtmann.org>
Compilation and installation
============================
In order to compile Bluetooth utilities you need following software packages:
- GCC compiler
- GLib library
- D-Bus library
- udev library (optional)
- readline (command line clients)
To configure run:
./configure --prefix=/usr --mandir=/usr/share/man \
--sysconfdir=/etc --localstatedir=/var
Configure automatically searches for all required components and packages.
To compile and install run:
make && make install
Configuration and options
=========================
For a working system, certain configuration options need to be enabled:
--enable-library
Enable installation of Bluetooth library
By default the Bluetooth library is no longer installed.
The user interfaces or command line utilities do not
require an installed Bluetooth library anymore. This
option is provided for legacy third party applications
that still depend on the library.
When the library installation is enabled, it is a good
idea to use a separate bluez-library or libbluetooth
package for it.
--disable-tools
Disable support for Bluetooth utilities
By default the Bluetooth utilities are built and also
installed. For production systems the tools are not
needed and this option allows to disable them to save
build time and disk space.
When the tools are selected, it is a good idea to
use a separate bluez-tools package for them.
--disable-cups
Disable support for CUPS printer backend
By default the printer backend for CUPS is build and
also installed. For systems that do not require printing
over Bluetooth, this options allows to disable it.
When the CUPS backend is selected, it is a good idea to
use a separate bluez-cups package for it.
--disable-monitor
Disable support for the Bluetooth monitor utility
By default the monitor utility is enabled. It provides
support for HCI level tracing and debugging. For systems
that don't require any kind of tracing or debugging
capabilities, this options allows to disable it.
The monitor utility should be placed in the main package
along with the daemons. It is universally useful.
--disable-client
Disable support for the command line client
By default the command line client is enabled and uses the
readline library. For specific systems where BlueZ is
configured by other means, the command line client can be
disabled and the dependency on readline is removed.
The client should be placed in the main package along
with the daemons. It is universally useful.
--disable-systemd
Disable integration with systemd
By default the integration with systemd is enabled and
installed. This gives the best integration into all
distributions based on systemd.
This option is provided for distributions that do not
support systemd. In that case all integration with the
init system is up to the package.
--disable-a2dp
Disable A2DP profile
By default bluetoothd supports A2DP profile using a built-in
plugin, this option disables it.
This option is provided for distributions that do not have any
audio capabilities.
--disable-avrcp
Disable AVRCP profile
By default bluetoothd supports AVRCP profile using a built-in
plugin, this option disables it.
This option is provided for distributions that do not have any
audio capabilities.
--disable-network
Disable PANU, NAP, GN profiles
By default bluetoothd supports PANU, NAP and GN profile using a
built-in plugin, this option disables it.
This option is provided for distributions that do not have any
network capabilities.
--enable-experimental
Enable experimental plugins
By default all plugins that are still in development
are disabled. This option can be used to enable them.
It is not recommended to enable this option for production
systems. The APIs or behavior of the experimental plugins
is unstable and might still change.
--enable-nfc
This option enable NFC pairing support.
By default the integration with neard is disabled, this gives
the option to enable it in system where neard is supported.
The plugin is built into bluetoothd therefore it does not need
to be package separately.
--enable-sap
This option enable SAP profile using sap plugin.
By default sap plugin is disabled since it requires tight
integration with systems and is very rarely required.
The plugin is built into bluetoothd therefore it does not need
to be package separately.
Information
===========
Mailing lists:
linux-bluetooth@vger.kernel.org
For additional information about the project visit BlueZ web site:
http://www.bluez.org
|
