From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: qt3 vs qt4 issues
Date: Mon, 26 Sep 2011 16:30:27 +0400 [thread overview]
Message-ID: <j5pran$mtt$1@dough.gmane.org> (raw)
In-Reply-To: <1DFC8F6E-C652-42A6-83B2-147A77A70A95@dominion.thruhere.net>
On 09/25/2011 06:50 PM, Koen Kooi wrote:
>
> Op 25 sep. 2011, om 13:33 heeft Richard Purdie het volgende geschreven:
>
>> I've been looking at the qt3 failures on the autobuilder. It seems there
>> is some kind of contamination between the qt4 builds and the qt3 builds
>> and I'm not sure what is or isn't expected to work there.
>>
>> We're doing the following in the build:
>>
>> a) Build core-image-lsb (includes qt4, builds qt4+qt4-native)
>> b) Wipe out tmp
>> c) Add in meta-qt3 layer
>> d) Enable sstate from build in a)
>> e) Build core-image-lsb-qt3 which adds in qt3
>> f) Bitbake determines it needs to install qt4 for the image but
>> nothing depends on the native qt4 tools so these are not installed
>> g) This will build qt3+qt3-native with qt4 in the sysroot but no
>> qt4-native
>> h) We see build failures as qt3 seems to want to find bits of qt4-native
>>
>> If qt4 and qt4-native are present, qt3 works
>> If qt4 and qt4-native are not present, qt3 works
>> If qt4 is present but qt4-native is not, qt3 fails
>>
>> How do we fix this?
>
> I suspect qt3 is missing bits of the tool renaming we do for qt4 and qt2 (moc, uic, lrelease, etc)
Most probably it's true. However for qt3 it can be harder, as qt4
already provides uic3, etc.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-09-26 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 11:33 qt3 vs qt4 issues Richard Purdie
2011-09-25 14:50 ` Koen Kooi
2011-09-26 12:30 ` Dmitry Eremin-Solenikov [this message]
2011-09-26 12:36 ` Richard Purdie
2011-09-26 13:58 ` Dmitry Eremin-Solenikov
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='j5pran$mtt$1@dough.gmane.org' \
--to=dbaryshkov@gmail.com \
--cc=openembedded-core@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.