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)
20 ./configure --prefix=/usr --mandir=/usr/share/man \
21 --sysconfdir=/etc --localstatedir=/var
23 Configure automatically searches for all required components and packages.
25 To compile and install run:
29 Configuration and options
30 =========================
32 For a working system, certain configuration options need to be enabled:
36 Enable installation of Bluetooth library
38 By default the Bluetooth library is no longer installed.
40 The user interfaces or command line utilities do not
41 require an installed Bluetooth library anymore. This
42 option is provided for legacy third party applications
43 that still depend on the library.
45 When the library installation is enabled, it is a good
46 idea to use a separate bluez-library or libbluetooth
51 Disable support for Bluetooth utilities
53 By default the Bluetooth utilities are built and also
54 installed. For production systems the tools are not
55 needed and this option allows to disable them to save
56 build time and disk space.
58 When the tools are selected, it is a good idea to
59 use a separate bluez-tools package for them.
63 Disable support for CUPS printer backend
65 By default the printer backend for CUPS is build and
66 also installed. For systems that do not require printing
67 over Bluetooth, this options allows to disable it.
69 When the CUPS backend is selected, it is a good idea to
70 use a separate bluez-cups package for it.
74 Disable support for the Bluetooth monitor utility
76 By default the monitor utility is enabled. It provides
77 support for HCI level tracing and debugging. For systems
78 that don't require any kind of tracing or debugging
79 capabilities, this options allows to disable it.
81 The monitor utility should be placed in the main package
82 along with the daemons. It is universally useful.
86 Disable support for the command line client
88 By default the command line client is enabled and uses the
89 readline library. For specific systems where BlueZ is
90 configured by other means, the command line client can be
91 disabled and the dependency on readline is removed.
93 The client should be placed in the main package along
94 with the daemons. It is universally useful.
98 Disable integration with systemd
100 By default the integration with systemd is enabled and
101 installed. This gives the best integration into all
102 distributions based on systemd.
104 This option is provided for distributions that do not
105 support systemd. In that case all integration with the
106 init system is up to the package.
108 --enable-experimental
110 Enable experimental plugins
112 By default all plugins that are still in development
113 are disabled. This option can be used to enable them.
115 It is not recommended to enable this option for production
116 systems. The APIs or behavior of the experimental plugins
117 is unstable and might still change.
124 linux-bluetooth@vger.kernel.org
126 For additional information about the project visit BlueZ web site: