Does anybody have experience using meta-qt5 and meta-ming together to
produce a usable SDK including Qt development tools for use on a Windows
host together?
The stock recipes for producing the nativesdk flavors of certain Qt
packages would seem to require some modification from vanilla meta-qt5
This is addressed with pull request #62:
From: Matt Hoosier <matt.hoos...@garmin.com>
>
> Date: Mon, 14 Aug 2017 08:04:03 -0500
>
> Subject: [PATCH 1/2] qtbase: fix Krogoth build regression from efa8aaf
>
>
>> With
>
>
>> commit efa8aaf82e580a7d32eaaa
Hi,
I observe that qtbase-native from jansa/master-5.9 fails on releases
versions of Yocto prior to 2.2 with a message like:
| +
> /home/hoosier/projects/consumer/tools/yocto/build/tmp/work/x86_64-linux/qtbase-native/5.9.1+gitAUTOINC+160533328c-r0/build/bin/qmake
>
On Fri, Aug 11, 2017 at 3:11 PM, Matt Hoosier <matt.hoos...@gmail.com>
wrote:
> Hi,
>
> I observe that qtbase-native from jansa/master-5.9 fails on releases
> versions of Yocto prior to 2.2 with a message like:
>
> | + /home/hoosier/projects/consumer/tools/yocto/build/
From: Matt Hoosier <matt.hoos...@garmin.com>
With
commit efa8aaf82e580a7d32eaaab48eb92d436f2e222a
Author: Andreas Müller <schnitzelt...@googlemail.com>
Date: Thu Feb 9 00:26:09 2017
qmake5_base.bbclass: set qt.conf by environment variable again
we stop
https://github.com/meta-qt5/meta-qt5/pull/62
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
On Thu, Aug 17, 2017 at 7:27 AM, Matt Hoosier <matt.hoos...@gmail.com> wrote:
>
> From: Matt Hoosier <matt.hoos...@garmin.com>
>
> With
>
> commit efa8aaf82e580a7d32eaaab48eb92d436f2e222a
> Author: Andreas Müller <schnitzelt...@googlemail.com>
On Mon, Aug 21, 2017 at 1:31 PM, Khem Raj wrote:
> On Mon, Aug 21, 2017 at 2:51 AM, Martin Jansa wrote:
>> I know it's not caused by this change, but it still creates "foodummy" file
>> in ${TOPDIR} can we please get rid of it or at least move it
Hi,
I'm searching for an annotation that I can insert (perhaps with a
.bbappend) into a recipe that indicates which of the multiple licensing
terms I elect to use for a given recipe.
The regular LICENSE_FLAGS_WHITELIST variable is somewhat related, but it
works in the opposite way: make an
interface.
The fixes are kept as a patch series for clarity.
Signed-off-by: Matt Hoosier
---
...utine-for-cleaning-recent-interfaces.patch | 60 +
...outine-for-tearing-down-an-interface.patch | 58 +
.../0003-Track-interface-socket-family.patch | 50 +
...0004-Use-list-for-changed
10 matches
Mail list logo