Re: How to upgrade Qt modules in daisy branch

[Alexander Kanavin <alex.kanavin@gmail.com>]

2018-08-09 12:10 GMT+02:00 Ankur Tyagi <ankur.tyagi85@gmail.com>:
> Our product is based upon 'daisy' branch (I know it's pretty old !) and now
> we have a need to support BLE in it (typical business case).
>
> My inner-self says it's the right time to upgrade everything but from
> business unit point of view, best would be to upgrade "just enough" to get
> BLE working.
>
> So I upgraded Bluez4.101 to Bluez5.46 which went well but when I started
> upgrading QtConnectivity from v5.4.1 to v5.11.0 then things started falling
> apart.
>
> It seems from v5.8 onward, Qt adopted new configuration system which is
> causing configuration and compilation failures when building QtConnectivity.
> Following change in recipe doesn't work.
>
> -PACKAGECONFIG[bluez] = "CONFIG+=OE_BLUEZ_ENABLED,,bluez4"
> +PACKAGECONFIG[bluez] = "-feature-bluez,-no-feature-bluez,bluez5"
>
>
> Is there a way I can upgrade QtConnectivity to v5.11 while staying on daisy
> branch ? Or is it just not possible to do so ?
>
> Any help is appreciated.

Staying close to upstream should be a continuous, ongoing activity,
and not a massive, disruptive effort when it's already too late :)

As for your specific need, it's basically not possible to tell what
you will need to fix and change. Recent version of Qt may need recent
versions of other things they depend on, and those recent other things
may pull in even more other recent things. They may even need a recent
C++ compiler which supports recent C++ standard, and when you bring in
that compiler, you will find that there's a ton of other things that
compiled before and need fixing now. The whole thing may quickly
unravel and become intractable - essentially you'll be upgrading the
whole stack while still calling it 'daisy'.

Alex