[oe] [PATCH] qwt: QT_LIBINFIX not being resolved when, running qmake

[Jayen Ashar]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm using the master branch for qwt, but I'm supporting an old fork of
OE, so I was using a snapshot at
cb429c4b7ae91b538603e771685aa39f020a5b6e (2009-06-24) for qt4-x11-free.

Thanks for that,
Jayen

- -------- Original Message --------
Subject: Openembedded-devel Digest, Vol 53, Issue 3
Date: Wed, 01 Dec 2010 09:55:55 +0100
From: openembedded-devel-request at lists.openembedded.org
Reply-To: openembedded-devel at lists.openembedded.org
To: openembedded-devel at lists.openembedded.org

Message: 2
Date: Wed, 01 Dec 2010 07:48:17 +0100
From: Eric B?nard <eric at eukrea.com>
Subject: Re: [oe] [PATCH] qwt: QT_LIBINFIX not being resolved when
	running qmake
To: openembedded-devel at lists.openembedded.org
Message-ID: <4CF5EFB1.2010000 at eukrea.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

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 at 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkz2xs0ACgkQGplE/Ggo/I5OlgCgoOw/af/XFsR/zebOMg4hQ+Ll
OTUAn2RwO/4SsKG6foVJIvvPNt3CCJjU
=O2SL
-----END PGP SIGNATURE-----