From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] qmake_base.bbclass: fix lrelease/lupdate binary names
Date: Thu, 2 Jun 2011 17:51:26 +0100 [thread overview]
Message-ID: <201106021751.26598.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <ac909be8f5af8515017da51e7217fc15ef69379e.1306958862.git.otavio@ossystems.com.br>
On Wednesday 01 June 2011 21:09:54 Otavio Salvador wrote:
> To support translation, qmake based projects usually call lrelease and
> lupdate however OE changes the binary names so this needs some mangle
> to work out of box.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> meta/classes/qmake_base.bbclass | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/meta/classes/qmake_base.bbclass
> b/meta/classes/qmake_base.bbclass index a054efd..165d689 100644
> --- a/meta/classes/qmake_base.bbclass
> +++ b/meta/classes/qmake_base.bbclass
> @@ -92,6 +92,11 @@ qmake_base_do_configure() {
> bbnote "qmake prevar substitution: ${EXTRA_QMAKEVARS_PRE}"
> fi
>
> + # Hack .pro files to use OE utilities
> + find -name '*.pro' \
> + -exec sed -i -e 's,=\s*.*/lrelease,= ${OE_QMAKE_LRELEASE},g' \
> + -e 's,=\s*.*/lupdate,= ${OE_QMAKE_LUPDATE},g' '{}' ';'
> +
> #bbnote "Calling '${OE_QMAKE_QMAKE} -makefile -spec ${QMAKESPEC} -o
> Makefile $QMAKE_VARSUBST_PRE $AFTER $PROFILES $QMAKE_VARSUBST_POST'" unset
> QMAKESPEC || true
> ${OE_QMAKE_QMAKE} -makefile -spec ${QMAKESPEC} -o Makefile
> $QMAKE_VARSUBST_PRE $AFTER $PROFILES $QMAKE_VARSUBST_POST || die "Error
> calling ${OE_QMAKE_QMAKE} on $PROFILES"
Acked-by: Paul Eggleton <paul.eggleton@linux.intel.com>
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-02 16:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 20:09 [PATCH 0/3] Patches pending on O.S. Systems tree Otavio Salvador
2011-06-01 20:09 ` [PATCH 1/3] busybox: enable mdev by default Otavio Salvador
2011-06-01 20:37 ` Phil Blundell
2011-06-01 20:40 ` Otavio Salvador
2011-06-02 16:37 ` Richard Purdie
2011-06-02 16:40 ` Otavio Salvador
2011-06-03 1:06 ` Khem Raj
2011-06-03 6:37 ` Koen Kooi
2011-06-03 8:24 ` Richard Purdie
2011-06-03 8:59 ` Koen Kooi
2011-06-03 9:50 ` Richard Purdie
2011-06-03 10:42 ` Koen Kooi
2011-06-03 9:57 ` Phil Blundell
2011-06-01 20:09 ` [PATCH 2/3] qmake_base.bbclass: fix lrelease/lupdate binary names Otavio Salvador
2011-06-02 16:51 ` Paul Eggleton [this message]
2011-06-02 17:27 ` Richard Purdie
2011-06-01 20:09 ` [PATCH 3/3] gnutls: link against 'dl' library Otavio Salvador
2011-06-01 20:33 ` Phil Blundell
2011-06-01 20:39 ` Otavio Salvador
2011-06-01 20:53 ` Phil Blundell
2011-06-01 21:00 ` Otavio Salvador
2011-06-01 21:43 ` Saul Wold
2011-06-01 21:52 ` Martin Jansa
2011-06-01 22:19 ` Saul Wold
2011-06-02 6:31 ` Martin Jansa
2011-06-02 9:29 ` Koen Kooi
2011-06-02 9:38 ` Richard Purdie
2011-06-02 11:00 ` [PATCH] gnutls: add --with-libdl-prefix and --with-libpthread-prefix Martin Jansa
2011-06-02 13:53 ` 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=201106021751.26598.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox