| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Change-Id: I57b18167dacb776a00d406e3faba6e780c764771
Reviewed-by: Paul Olav Tvete <paul.tvete@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
The QtBluetooth library only builds the bluez backend when qtdbus is
enabled. Previously it was possible that dbus was disabled but the bluez
feature flag is still set. This patch prevents this gap by directly
binding the bluez feature to the dbus feature.
Change-Id: I173d51f27f5b1a78241548617f602830fec7bb14
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BlueZ is the only platform that requires to set the BTLE address type.
The patch introduces a new UI button which allows the user to toggle
the address type.
The UI element is disabled on all platforms but Linux/BlueZ systems.
The number of devices returned in simulator mode is reduced to
four devices. This was done purely for esthetical reasons as the
additional address type button takes screen real estate away and
five simulator devices require more screen real estate than the
remaining space for device list. This avoid the need for scrolling.
Change-Id: I14cf26b3c821db7768b9d018c2d09441cd97679a
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
|
|
Properly do the detection of bluez and the linux crypto API,
and don't run pkg-config at build time.
Change-Id: I0f082992c0f82e90e611283ff0c2cc0143e74bd6
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
|
