QtConnectivity with Bluez compiled from sources

Mark81 · wrote on 17 Jun 2016, 10:06

QtConnectivity compiles successfully but with the "dummy backend".
Usually one must install the development packages for bluez, but I compiled it from sources.

How can I "tell" this to Qt5?

Mark81 · wrote on 17 Jun 2016, 12:30

I found the bluez.pc file is created during compilation but for some reasons is not installed. I manually copied it to /usr/lib/pkg-config/. Now pkg-config --modversion bluez finds it and it seems the test of qtconnectivity are ok.

But the warning about the dummy backend is still there...

SGaist · 19 Jun 2016, 07:35

Hi,

Did you rebuild the module from scratch once your installed bluez ?

Mark81 · S SGaist 17 Jun 2016, 22:05

@SGaist yes I did, but I've ended up to rebuild ALL. Perhaps make clean in the submodule directory wasn't enough?

SGaist · 26 Jun 2016, 11:16

When you recompiled the module did bluez got found ?

Mark81 · S SGaist 19 Jun 2016, 20:35

@SGaist There were no explicit messages, they seems to appear only during the configuration step.

SGaist · 28 Jun 2016, 08:31

AFAIK, yes, the detection is done when you configure the module.

micland · S SGaist 26 Jun 2016, 20:49

@SGaist said:

AFAIK, yes, the detection is done when you configure the module.

Unfortunately not. The configure script only checks the dependencies of qtbase. bluez is detected when running qmake for qtconnectivity and will print out a the little message Unsupported bluetooth platform, will not build a working QtBluetooth library if bluez was not found...

SGaist · 28 Jun 2016, 09:21

@micland good point, I was thinking about the checking phase that is done when qmake is run on the module. One of the most visible for that being qtmultimedia.

A side note, IIRC if you re-run qmake on an already "configured" module, the detection won't be done again. You have to delete the .qmake.cache file to have it happening again or just nuke the folder and start from a clean state.

micland · S SGaist 28 Jun 2016, 08:50

@SGaist
Ah right - "configure" is ambiguous due to the two step configuration, once by the configure script for qtbase and once by the qmake for the other modules.
This is not so obviously that the summary of the configure script does not warn about disabled features in submodules due to missing dependencies.