All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH v6] Upgrade to Qt 5.8
Date: Thu, 26 Jan 2017 21:03:38 +0100	[thread overview]
Message-ID: <20170126200338.GC3016@jama> (raw)
In-Reply-To: <1485442490-2464-1-git-send-email-samuli.piippo@qt.io>

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

On Thu, Jan 26, 2017 at 04:54:50PM +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.
> 
> The new Qt configuration system [1] can be used with a new variable
> EXTRA_QMAKEVARS_CONFIGURE, which takes both command line and feature
> arguments.
> 
> Merge the two qtwayland recipes to one that supports all three targets
> (target, native, nativesdk) without need for additional patch.
> 
> Recipes for new Qt modules: QtSCXML, QtNetworkAuth, QtGamepad.
> Removes qtdeclarative-render2d

Thanks this resolved the -no-alsa issue, now it failing a bit further
with:

|
/OE/build/oe-core/tmp-glibc/work/i586-oe-linux/qtwebkit/5.8.0+gitAUTOINC+74ac5b0f34-r0/git/Source/ThirdParty/ANGLE/src/compiler/preprocessor/Tokenizer.l:2779:26:
error: 'yylex_destroy' was not declared in this scope

which might be caused by flex upgrade as I'm seeing similar issues in
other recipes and Khem reported the same here:
http://lists.openembedded.org/pipermail/openembedded-core/2017-January/131555.html
and Patrick here:
http://lists.openembedded.org/pipermail/openembedded-core/2017-January/131326.html

Hopefully there will be upgrade to flex-2.6.3 to test this completely.

> [1] https://www.mail-archive.com/development@qt-project.org/msg25257.html
> 
> Change-Id: Ib37c4d7323e8b45aa2b171e8427b6ec15aaee213
> Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2017-01-26 20:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 14:54 [meta-qt5][PATCH v6] Upgrade to Qt 5.8 Samuli Piippo
2017-01-26 20:03 ` Martin Jansa [this message]
2017-01-27 16:36   ` Martin Jansa
2017-02-07  8:22     ` Andreas Müller
2017-02-07  9:02       ` Andreas Müller
2017-02-07 15:56 ` Andreas Müller

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=20170126200338.GC3016@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.