藍牙 API 提供藍牙使能設備之間的連接。
目前，API 支持下列平颱：
| API 特徵 | Android | iOS | Linux (BlueZ 5.x) | macOS | Windows |
|---|---|---|---|---|---|
| 經典藍牙 | x | x | x | x | |
| 藍牙 LE 中心 | x | x | x | x | x |
| 藍牙 LE 外圍 | x | x | x | x |
Bluetooth is a short-range (less than 100 meters) wireless technology. It has a data transfer rate of 2.1 Mbps, which makes it ideal for transferring data between devices. Bluetooth connectivity is based on basic device management, such as scanning for devices, gathering information about them, and exchanging data between them.
Qt Bluetooth supports Bluetooth Low Energy development for client/central role use cases. Further details can be found in the 低功耗藍牙概述 章節。
使用 Qt 模塊的 C++ API 要求直接 (或透過其它依賴) 鏈接到模塊庫。幾個構建工具對此有專用支持，包括 CMake and qmake .
使用
find_package()
命令定位所需模塊組件在
Qt6
包：
find_package(Qt6 REQUIRED COMPONENTS Bluetooth)
target_link_libraries(mytarget PRIVATE Qt6::Bluetooth)
更多細節，見 構建采用 CMake 概述。
要配置采用 qmake 構建模塊，添加模塊作為值為
QT
變量在工程的 .pro 文件：
QT += bluetooth
Starting from Qt 6.6, the Qt Bluetooth module uses new QPermission API 處理 藍牙 權限。這意味著 Qt 自身不再查詢這些權限，所以，做到這需要直接從客戶端應用程序。
請參考 應用程序權限 頁瞭解範例如何集成新 QPermission API 進應用程序。
Even though the module can be built for all Qt platforms, the module is not ported to all of them. Non-supported platforms employ a dummy backend that is automatically selected when the platform is not supported. The dummy backend reports appropriate error messages and values, which enables you to detect at runtime that the current platform is not supported. The dummy backend is also selected on Linux if BlueZ development headers are not found during build time or Qt was built without Qt D-Bus support.
The usage of the dummy backend is highlighted via an appropriate warning while building and running.
Since Qt 6.5 the Linux peripheral support has two backend alternatives: BlueZ DBus and Bluetooth Kernel API. The DBus backend is the default backend since Qt 6.7.
BlueZ DBus is the newer BlueZ stack and possibly the eventual successor of the older Kernel API. It is a bit more limited in terms of features, but in a typical usage this should not matter. One notable benefit of using the DBus backend is that the user process no longer needs to have the
CAP_NET_ADMIN
capability (for example by running as
root
user).
The DBus backend requires BlueZ version 5.56 or higher, and that it provides the needed DBus APIs. If these requirements are not met, Qt automatically falls back to the Bluetooth Kernel API backend.
The older kernel backend can also be selected manually by setting the QT_BLUETOOTH_USE_KERNEL_PERIPHERAL 環境變量。
The Bluetooth API on macOS requires a certain type of event dispatcher that in Qt causes a dependency to
QGuiApplication
. However, you can set the environment variable
QT_EVENT_DISPATCHER_CORE_FOUNDATION=1
to circumvent this issue.
Applications that don't use Classic Bluetooth will find a subset of QtBluetooth is available, as CoreBluetooth (Bluetooth LE) don't require QApplication or QGuiApplication .
The QtBluetooth 模塊導齣下列 日誌類彆 :
| 日誌類彆 | 描述 |
|---|---|
| qt.bluetooth | Enables logging of cross platform code path in QtBluetooth |
| qt.bluetooth.android | Enables logging of the Android 實現 |
| qt.bluetooth.bluez | Enables logging of the BLuez/Linux implementation |
| qt.bluetooth.ios | Enables logging of the iOS 實現 |
| qt.bluetooth.osx | Enables logging of the macOS 實現 |
| qt.bluetooth.windows | Enables logging of the Windows 實現 |
Logging categories enable additional warning and debug output for
QtBluetooth
. More detailed information about logging is found in
QLoggingCategory
. A quick way to enable all
QtBluetooth
logging is to add the following line to the
main()
函數：
QLoggingCategory::setFilterRules(QStringLiteral("qt.bluetooth* = true"));
Changes to Qt Bluetooth 列齣瞭 Qt 的 Qt 6 係列在模塊 API 和功能上所做齣的重要改變。
Qt Bluetooth 在商業許可下是可用的來自 Qt 公司 。此外，它是可用的根據 GNU LGPL (次一般公共許可) 第 3 版 ，或 GNU GPL (一般公共許可) 第 2 版 。見 Qt 許可 進一步瞭解細節。
在 Linux，Qt Bluetooth 使用單獨可執行文件
sdpscanner
, to integrate with the official Linux bluetooth protocol stack BlueZ. BlueZ is available under the
GNU GPL (一般公共許可) 第 2 版
.
| GNU General Public License v2.0 only (This does not force user code to be GPL'ed. For more info see details.) |