Re: [meta-qt5][master][jethro][PATCH] qtconnectivity, qtsystems: fix bluetooth support

[Javier Viguera <javier.viguera@digi.com>]

On 04/01/16 21:37, Martin Jansa wrote:
> So you can build both with:
> bitbake -c build bluez5 bluez4
> (or with "bitbake world")
> 
> and you end with 2 providers for bluez.pc (and bluetooth.so) in the sysroot
> and qtconnectivity will get runtime dependency on whatever bluez version
> was built first, e.g. bluez5 even when BLUEZ variable says bluez4. See
> shlibs provider code in package.bbclass.
> 
> That's cause for undeterministic builds and this QA warning:
> WARNING: QA Issue: qtconnectivity rdepends on bluez5, but it isn't a build dependency? [build-deps]

Ok, I understand now the problem. Thanks for explaining it.

But to be honest, I don't know how this can be solved in these QT5 recipes. To me this seems more a problem in the bluez5 recipe, so it cannot be built when bluez4 is already built. This is probably beyond my Yocto skills :-)

I used this commit as an example to add the bluez5 support:

http://git.openembedded.org/meta-openembedded/commit/?id=c2069a1420fb3d199c99f8b6e778478240fa56be

Shouldn't the problem you outline happen just the same with the gpsd recipe after above commit?

-- 
Regards,

Javier Viguera