[SailfishDevel] Using QtBluetooth 5.4 Backport in a harbour-app
aaron.mccarthy at jolla.com
Mon Jan 5 00:56:57 UTC 2015
On Mon, 15 Dec 2014 17:53:34 Harald Schmitt wrote:
> Am 15.12.2014 um 13:35 schrieb Harald Schmitt:
> > Am 11.12.2014 um 17:45 schrieb Harald Schmitt:
> >> Am 10.12.2014 um 18:24 schrieb Richard Rondu:
> >>> Hi, the backport is not completely up-to-date with QtBluetooth 5.4, I
> >>> have to update it. Nevertheless It should work with standard
> >>> bluetooth, I haven't tried with BLE though.
> >>> Other part of QtConnectivity that are not QtBluetooth haven't been
> >>> tried either (NFC and so on). I even think I have even disabled the
> >>> build.
> >>> Nevertheless, here are the relevant part of the .yaml file and the
> >>> .pro file I use for "Parrot ZIK 2.0 Manager" in harbour that ship
> >>> with this backport.
> >>> You have to build QtBluetooth backport separately with the sailfish
> >>> sdk, then put the .so file(s) in a "lib" subdirectory inside your
> >>> project.
> >> thanks that got me started. I hope I can dedicate enough time to bring a
> >> Xiaomi MiBand app to the harbour.
> > While building qtconnectivity with the sdk I get the following message
> > Project MESSAGE: Unsupported Bluetooth platform, will not build a
> > working QtBluetooth library.
> > Project MESSAGE: Either no Qt D-Bus found or no BlueZ headers.
> > qtHaveModule(dbus) returns false. Do you have any idea?
> I made a mistake, actually config_bluez returns false and
> qtHaveModule(dbus) returns true. But still I don't know why.
Try to determine why the BlueZ config test failed. You can manually try to
build the config test project in qtconnectivity/config.tests/bluez. It uses
pkgconfig to find the required headers and libraries. Ensure that the required
development packages are installed.
More information about the Devel