From: Philip Balister <philip@balister.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] qt4.inc : Add uic, moc, rcc, and lrelease to tools package.
Date: Wed, 07 Dec 2011 11:44:10 -0500 [thread overview]
Message-ID: <4EDF97DA.1070009@balister.org> (raw)
In-Reply-To: <DCF0DA43-34BE-4AD2-8E13-536E6DCDF49A@dominion.thruhere.net>
On 12/07/2011 11:23 AM, Koen Kooi wrote:
>
> Op 7 dec. 2011, om 16:59 heeft Philip Balister het volgende geschreven:
>
>> These binaries are needed in the target tools package so we can build
>> qt apps on the target. You also need to install qmake from meta-oe.
>>
>> Test by building gnuradio on the USRP e100 with qt support.
>>
>> Signed-off-by: Philip Balister <philip@balister.org>
>> ---
>> meta/recipes-qt/qt4/qt4.inc | 9 ++-------
>> 1 files changed, 2 insertions(+), 7 deletions(-)
>>
>> diff --git a/meta/recipes-qt/qt4/qt4.inc b/meta/recipes-qt/qt4/qt4.inc
>> index bec81b4..2638249 100644
>> --- a/meta/recipes-qt/qt4/qt4.inc
>> +++ b/meta/recipes-qt/qt4/qt4.inc
>> @@ -138,8 +138,8 @@ RRECOMMENDS_${QT_BASE_NAME}-qmlviewer += " \
>> RRECOMMENDS_${QT_BASE_NAME}-doc += " \
>> ${QT_BASE_NAME}-demos-doc"
>>
>> -FILES_${QT_BASE_NAME}-tools = "${bindir}/qttracereplay ${bindir}/qdoc*"
>> -FILES_${QT_BASE_NAME}-tools-dbg = "${bindir}/.debug/qttracereplay ${bindir}/.debug/qdoc*"
>> +FILES_${QT_BASE_NAME}-tools = "${bindir}/qttracereplay ${bindir}/qdoc* ${bindir}/moc ${bindir}/uic* ${bindir}/rcc"
>> +FILES_${QT_BASE_NAME}-tools-dbg = "${bindir}/.debug/qttracereplay ${bindir}/.debug/qdoc* ${bindir}/.debug/uic* ${bindir}/.debug/moc ${bindir}/.debug/rcc"
>> FILES_${QT_BASE_NAME}-assistant = "${bindir}/*assistant* ${bindir}/qcollectiongenerator ${bindir}/qhelpconverter ${bindir}/qhelpgenerator"
>> FILES_${QT_BASE_NAME}-assistant-dbg = "${bindir}/.debug/*assistant* ${bindir}/.debug/qcollectiongenerator ${bindir}/.debug/qhelpconverter ${bindir}/.debug/qhelpgenerator"
>> FILES_${QT_BASE_NAME}-common = "${bindir}/qtconfig"
>> @@ -287,11 +287,6 @@ do_install() {
>>
>> # These are host binaries, we should only use them in staging
>> rm ${D}/${bindir}/qmake
>> - rm -f ${D}/${bindir}/uic
>> - rm -f ${D}/${bindir}/uic3
>> - rm ${D}/${bindir}/moc
>> - rm ${D}/${bindir}/rcc
>> - rm -f ${D}/${bindir}/lrelease
>
> Can you verify that those are actually target binaries and not x86 ones?
root@usrp-e1xx:~# file /usr/bin/lrelease
/usr/bin/lrelease: ELF 32-bit LSB executable, ARM, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.16, stripped
root@usrp-e1xx:~# file /usr/bin/rcc
/usr/bin/rcc: ELF 32-bit LSB executable, ARM, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.16, stripp
root@usrp-e1xx:~# file /usr/bin/moc
/usr/bin/moc: ELF 32-bit LSB executable, ARM, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.16, stripped
root@usrp-e1xx:~# file /usr/bin/uic3
/usr/bin/uic3: ELF 32-bit LSB executable, ARM, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.16, stripp
root@usrp-e1xx:~# file /usr/bin/uic
/usr/bin/uic: ELF 32-bit LSB executable, ARM, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.16, stripped
Philip
>
> regards,
>
> Koen
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-12-07 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:59 [PATCH 1/2] boost : Add icu to DEPENDS to fix a build failure Philip Balister
2011-12-07 15:59 ` [PATCH 2/2] qt4.inc : Add uic, moc, rcc, and lrelease to tools package Philip Balister
2011-12-07 16:23 ` Koen Kooi
2011-12-07 16:44 ` Philip Balister [this message]
2011-12-07 17:31 ` Paul Eggleton
2011-12-07 16:40 ` [PATCH 1/2] boost : Add icu to DEPENDS to fix a build failure Richard Purdie
2011-12-07 16:49 ` Philip Balister
2011-12-07 18:23 ` Richard Purdie
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=4EDF97DA.1070009@balister.org \
--to=philip@balister.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox