Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

I've fixed the gcc7 + security_flags.inc issues in 5.8.0, that's now merged in master. Then I've rebased Samuli's upgrade to 5.9.0 to build on top of that and added another upgrade to 5.9.2. That's currently in master-next branch. But there is still this issue with qemux86 on x86_64 builders, so

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

On Fri, Jun 23, 2017 at 2:58 AM, Trevor Woerner wrote: > On Thu, Jun 22, 2017 at 3:35 PM, Denys Dmytriyenko wrote: >> On Thu, Jun 15, 2017 at 01:25:12AM -0400, Trevor Woerner wrote: >>> On Fri, Jun 9, 2017 at 4:16 AM, Martin Jansa

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

On Thu, Jun 22, 2017 at 3:35 PM, Denys Dmytriyenko wrote: > On Thu, Jun 15, 2017 at 01:25:12AM -0400, Trevor Woerner wrote: >> On Fri, Jun 9, 2017 at 4:16 AM, Martin Jansa wrote: >> > Then why does it work for chromium which used to have the same issue?

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

On Thu, Jun 15, 2017 at 01:25:12AM -0400, Trevor Woerner wrote: > On Fri, Jun 9, 2017 at 4:16 AM, Martin Jansa wrote: > > Then why does it work for chromium which used to have the same issue? > >

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

On Fri, Jun 9, 2017 at 4:16 AM, Martin Jansa wrote: > Then why does it work for chromium which used to have the same issue? https://github.com/OSSystems/meta-browser/blob/master/recipes-browser/chromium/chromium/chromium/m32.patch --

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

I could not say. The origin bugreport that changed this for QtWebEngine was https://bugreports.qt.io/browse/QTBUG-59504 On 09.06.2017 11:16, Martin Jansa wrote: Then why does it work for chromium which used to have the same issue? On Fri, Jun 9, 2017 at 7:15 AM, Samuli Piippo

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

Then why does it work for chromium which used to have the same issue? On Fri, Jun 9, 2017 at 7:15 AM, Samuli Piippo wrote: > That's done on purpose, the tools are built with same bitness as the > target. > This is why you need to have gcc-multilib available on the build

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

Still passes incorrect -m32 when building host tools on 64bit when the target is 32bit e.g. qemux86 http://errors.yoctoproject.org/Errors/Details/144181/ On Thu, Jun 8, 2017 at 2:53 PM, Martin Jansa wrote: > Thanks, will include v3 in next build. > > Full report with v2

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

Thanks, will include v3 in next build. Full report with v2 included: http://lists.openembedded.org/pipermail/openembedded-devel/2017-June/113073.html There is another issue in qtwebview, which should have the same restriction as qtwebengine otherwise for qemuarm it causes: * ERROR: Nothing

Re: [oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

Patch updated to fix build issues with qtlocation and qtremoteobjects On 08.06.2017 15:30, Samuli Piippo wrote: * adapt QtWebEngine recipe to use GN instead of GYP * add QtRemoteObjects and QtWebView as a new Qt modules * update available QtBase configure arguments * remove obsolete patches *

[oe] [meta-qt5][PATCH v3] Upgrade to Qt 5.9.0

* adapt QtWebEngine recipe to use GN instead of GYP * add QtRemoteObjects and QtWebView as a new Qt modules * update available QtBase configure arguments * remove obsolete patches * patch all .pc files to remove build paths * include generated QML cache files in packages * the patch "configure