All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ankur Tyagi <ankur.tyagi85@gmail.com>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: How to upgrade Qt modules in daisy branch
Date: Thu, 9 Aug 2018 22:10:29 +1200	[thread overview]
Message-ID: <CADySD0EZ05doNyBhkT6v3K4ibTVp5wtXJ2zY9YwYWGri_n5QOw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 968 bytes --]

Hi,

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.

Thanks
Ankur

[-- Attachment #2: Type: text/html, Size: 2502 bytes --]

             reply	other threads:[~2018-08-09 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09 10:10 Ankur Tyagi [this message]
2018-08-09 12:26 ` How to upgrade Qt modules in daisy branch Alexander Kanavin
2018-08-09 12:40 ` Martin Jansa
2018-08-09 16:16   ` Andreas Müller
2018-08-09 19:56     ` Ankur Tyagi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADySD0EZ05doNyBhkT6v3K4ibTVp5wtXJ2zY9YwYWGri_n5QOw@mail.gmail.com \
    --to=ankur.tyagi85@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.