From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: Updating daisy -> Python.h not found
Date: Sat, 18 Oct 2014 11:19:14 +0200 [thread overview]
Message-ID: <m1tbak$ko0$1@ger.gmane.org> (raw)
In-Reply-To: <20141018091009.GD2437@jama>
Am 18.10.2014 um 11:10 schrieb Martin Jansa:
> On Sat, Oct 18, 2014 at 10:51:30AM +0200, Neuer User wrote:
>> Btw. do you know that the qt5 repo is currently incompatible with daisy?
>> There is a patch in fsl-arm that cannot be applied:
>>
>> ./meta-fsl-arm/qt5-layer/recipes-qt/qt5/qtmultimedia_%.bbappend
>>
>> This needs to be deleted, otherwise qtmultimedia cannot be generated.
>
> Are you using meta-qt5/daisy or meta-qt5/master?
>
Hmm, master. Didn't know there was a daisy branch. Did a diff between
the two branches now and do not see any difference though which could
solve the above problem (just seems to add some things such as
noqtwebkit option). I will try it though.
> Please report it to meta-fsl-arm maintainer, I'm not using that layer,
> but I think they should either provide separate .bbappends for _5.*.bb and
> *_git.bb or make sure it applies for both versions (there is 5.3.2 and
> 5.4-alpha in meta-qt5/master and many patches need to be slightly
> different).
>
Ok. will send that to the maintainer.
Cheers
Michael
P.S.: My yocto install is still compiling but I already saw that the
error is still there. So I will now try to revert the two patches you
mentioned.
next prev parent reply other threads:[~2014-10-18 9:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 10:00 Updating daisy -> Python.h not found Neuer User
2014-10-17 14:51 ` Paul Eggleton
2014-10-17 15:01 ` Neuer User
2014-10-17 15:05 ` Paul Eggleton
2014-10-17 15:19 ` Neuer User
2014-10-17 16:09 ` Neuer User
2014-10-18 7:11 ` Neuer User
2014-10-18 8:44 ` Martin Jansa
2014-10-18 8:51 ` Neuer User
2014-10-18 9:10 ` Martin Jansa
2014-10-18 9:19 ` Neuer User [this message]
2014-10-18 9:36 ` Martin Jansa
2014-10-18 9:32 ` SOLUTION: " Neuer User
2014-10-18 10:03 ` Martin Jansa
2014-10-18 21:20 ` Tyler Hall
2014-10-18 21:33 ` Tyler Hall
2014-10-19 6:16 ` Neuer User
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='m1tbak$ko0$1@ger.gmane.org' \
--to=auslands-kv@gmx.de \
--cc=yocto@yoctoproject.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.