All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ankur Tyagi <ankur.tyagi85@gmail.com>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: How to upgrade Qt modules in daisy branch
Date: Fri, 10 Aug 2018 07:56:46 +1200	[thread overview]
Message-ID: <CADySD0HR+pdE8GipDH72Mo6ZD0OBiRz--ub1NwG2ranWgr0S5A@mail.gmail.com> (raw)
In-Reply-To: <CALbNGRRpOXtZXgnJWAx2Ut5V3TM_LZx6LYokqOfzhW_G5vX3Ew@mail.gmail.com>

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

Thank you Andreas, Martin and Alex for your responses.

I will follow your leads and hopefully will be able to do it.

Regards
Ankur

On Fri 10 Aug, 2018, 4:16 AM Andreas Müller, <schnitzeltony@gmail.com>
wrote:

> On Thu, Aug 9, 2018 at 2:40 PM, Martin Jansa <martin.jansa@gmail.com>
> wrote:
> > For daisy you probably don't have support for PACKAGECONFIG_CONFARGS
> which
> > was added in Yocto 2.1 krogoth.
> >
> I remember doing similar for other reasons. We have images based on
> jethro (ok - daisy is a bit older) with later Qt's. Our builds are
> based on [1] but I created branches up to Qt5.9 (stable release - but
> not updated to latest) [2] for jethro.
>
> It's not daisy - not Qt5.11 - no guarantees - but maybe a start.
>
> [1] https://github.com/schnitzeltony/meta-qt5/tree/jethro+5.7
> [2] https://github.com/schnitzeltony/meta-qt5/tree/jethro+5.9
>
> Andreas
>

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

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

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

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=CADySD0HR+pdE8GipDH72Mo6ZD0OBiRz--ub1NwG2ranWgr0S5A@mail.gmail.com \
    --to=ankur.tyagi85@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=schnitzeltony@gmail.com \
    /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.