QtConnectivity with Bluez compiled from sources
-
wrote on 17 Jun 2016, 10:06 last edited by
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?
-
wrote on 17 Jun 2016, 12:30 last edited by
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...
-
Hi,
Did you rebuild the module from scratch once your installed bluez ?
-
When you recompiled the module did bluez got found ?
-
AFAIK, yes, the detection is done when you configure the module.
-
wrote on 28 Jun 2016, 08:31 last edited by
@SGaist said:
AFAIK, yes, the detection is done when you configure the module.
Unfortunately not. The
configurescript 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... -
@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.cachefile to have it happening again or just nuke the folder and start from a clean state. -
@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.cachefile to have it happening again or just nuke the folder and start from a clean state.wrote on 28 Jun 2016, 09:21 last edited by@SGaist
Ah right - "configure" is ambiguous due to the two step configuration, once by theconfigurescript 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.
10/10