From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCHv2] Upgrade to Qt 5.8
Date: Wed, 23 Nov 2016 19:52:51 +0100 [thread overview]
Message-ID: <20161123185251.GG3265@jama> (raw)
In-Reply-To: <20161123154346.GD3265@jama>
[-- Attachment #1: Type: text/plain, Size: 3078 bytes --]
On Wed, Nov 23, 2016 at 04:43:46PM +0100, Martin Jansa wrote:
> On Wed, Nov 23, 2016 at 04:29:41PM +0100, Martin Jansa wrote:
> > On Fri, Nov 18, 2016 at 09:48:54AM +0200, Samuli Piippo wrote:
> > > The linux-oe-g++ mkspec is changed to use $$(...) operator to obtain
> > > the contents of an environment value when qmake is run instead of when
> > > Makefile is processed. All OE_QMAKE_xxx variables need to be exported
> > > for qmake to find them. configure's setBootstrapVariable function needs
> > > to change $$(..) to normal $(...) operator to work with qmake's Makefile.
> > >
> > > qt.conf generation for qtbase recipes is not needed, as configure will
> > > generate its own version based on configure arguments. Skip running
> > > qmake, since configure is now automatically invoked when it's run in
> > > qtbase's root folder.
> > >
> > > Update PACKAGECONFIGs for qtbase to match current configure options.
> > >
> > > Merge the two qtwayland recipes to one that supports all three targets
> > > (target, native, nativesdk) without need for additional patch.
> > >
> > > Change-Id: Ib37c4d7323e8b45aa2b171e8427b6ec15aaee213
> > > Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
> > > ---
> ...
> > > diff --git a/recipes-qt/qt5/qt5-git.inc b/recipes-qt/qt5/qt5-git.inc
> > > index e1e25ba..a1dd16a 100644
> > > --- a/recipes-qt/qt5/qt5-git.inc
> > > +++ b/recipes-qt/qt5/qt5-git.inc
> > > @@ -2,7 +2,7 @@
> > > # Copyright (C) 2013-2016 Martin Jansa <martin.jansa@gmail.com>
> > >
> > > QT_MODULE ?= "${BPN}"
> > > -QT_MODULE_BRANCH ?= "5.7"
> > > +QT_MODULE_BRANCH ?= "5.8"
> > > QT_MODULE_BRANCH_PARAM ?= "branch=${QT_MODULE_BRANCH}"
> > >
> > > # each module needs to define valid SRCREV
> > > @@ -12,4 +12,4 @@ SRC_URI = " \
> > >
> > > S = "${WORKDIR}/git"
> > >
> > > -PV = "5.7.0+git${SRCPV}"
> > > +PV = "5.8.0+git${SRCPV}"
> >
> > This version is wrong as 5.8.0 wasn't released yet (was it?), so this PV
> > shouldn't sort higher then 5.8.0 release.
> >
> > I'll change it to:
> > 5.7.99+5.8.0-beta+git${SRCPV}
> > like I did in previous releases.
> >
> > Regards,
> ...
>
> There is also some issue with qtwayland and qtenginio reported in:
> http://lists.openembedded.org/pipermail/openembedded-devel/2016-November/110021.html
>
> I'm trying to reproduce it with only oe-core+meta-qt5, because the qtwayland
> one might be caused by bbappend in meta-luneui, but qtenginio might be
> easier to reproduce.
Local build confirmed that qtwayland issue was caused by that bbappend,
but qtenginio error is still there and I've also noticed that with:
PACKAGECONFIG_append_pn-qtbase = " icu gl accessibility directfb examples kms"
PACKAGECONFIG_remove_pn-qtbase = "gl"
qtbase.do_compile fails with:
http://errors.yoctoproject.org/Errors/Details/107134/
and this configuration was working with 5.7 version, is directfb
unsupported now in 5.8 or does it just need some tweaks in qtbase
PACKAGECONFIGs?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2016-11-23 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 7:48 [meta-qt5][PATCHv2] Upgrade to Qt 5.8 Samuli Piippo
2016-11-23 15:29 ` Martin Jansa
2016-11-23 15:43 ` Martin Jansa
2016-11-23 18:52 ` Martin Jansa [this message]
2016-11-23 20:14 ` Martin Jansa
2016-11-24 8:23 ` Samuli Piippo
2016-11-24 10:47 ` Martin Jansa
2016-11-25 6:07 ` Samuli Piippo
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=20161123185251.GG3265@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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.