All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] qwt: QT_LIBINFIX not being resolved when running qmake
Date: Wed, 01 Dec 2010 07:48:17 +0100	[thread overview]
Message-ID: <4CF5EFB1.2010000@eukrea.com> (raw)
In-Reply-To: <1291178841-3975-1-git-send-email-jayen@cse.unsw.edu.au>

On 01/12/2010 05:47, Jayen Ashar wrote:
> Fixed a problem where qmake would create a directory called 'obj${QT_LIBINFIX}'
> instead of resolving the QT_LIBINFIX variable and creating the appropriately
> resolved directory.
>
> Signed-off-by: Jayen Ashar<jayen@cse.unsw.edu.au>
> ---
>   recipes/qwt/qwt.inc |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/recipes/qwt/qwt.inc b/recipes/qwt/qwt.inc
> index 62c8656..89035c1 100644
> --- a/recipes/qwt/qwt.inc
> +++ b/recipes/qwt/qwt.inc
> @@ -10,7 +10,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/qwt/qwt-${PV}.tar.bz2;name=qwt"
>   S = "${WORKDIR}/qwt-${PV}"
>
>   do_configure_prepend() {
> -	sed -i -e 's:RELEASE_SUFFIX      = :RELEASE_SUFFIX      = ${QT_LIBINFIX}:' *.pri
> +	sed -i -e 's:RELEASE_SUFFIX      = :RELEASE_SUFFIX      = $\${QT_LIBINFIX}:' *.pri
>   	sed -i -e s:lqwt:lqwt${QT_LIBINFIX}:g -e s:/usr/local/qwt-$\${QwtVersion}:${prefix}:g *.prf
>   	sed -e 's/#CONFIG     += QwtExamples/CONFIG     += QwtExamples/g' -i qwtconfig.pri
>   	sed -i -e s:/usr/local/qwt-${PV}:${D}${prefix}:g ${S}/*.pri

Are you using the release branch ?

this should be fixed in 26002b31b7232ee71249cc39fd8184d80ecb9ec2

Eric



  reply	other threads:[~2010-12-01  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01  4:47 [PATCH] qwt: QT_LIBINFIX not being resolved when running qmake Jayen Ashar
2010-12-01  6:48 ` Eric Bénard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-01 22:06 [PATCH] qwt: QT_LIBINFIX not being resolved when, " Jayen Ashar

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=4CF5EFB1.2010000@eukrea.com \
    --to=eric@eukrea.com \
    --cc=openembedded-devel@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.