From: Jonathan Liu <net147@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qt4e.bbclass: export OE_QMAKE_QT_CONFIG
Date: Fri, 28 Jun 2013 22:07:02 +1000 [thread overview]
Message-ID: <51CD7C66.3020702@gmail.com> (raw)
In-Reply-To: <1371254791-8168-1-git-send-email-net147@gmail.com>
On 15/06/2013 10:06 AM, Jonathan Liu wrote:
> The class is inheriting qmake2.bbclass which exports OE_QMAKE_QT_CONFIG
> pointing to the qt4 qconfig.pri when it should be pointing to the
> qt4-embedded qconfig.pri.
>
> Signed-off-by: Jonathan Liu <net147@gmail.com>
> ---
> meta/classes/qt4e.bbclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/qt4e.bbclass b/meta/classes/qt4e.bbclass
> index de2a68d..13b1050 100644
> --- a/meta/classes/qt4e.bbclass
> +++ b/meta/classes/qt4e.bbclass
> @@ -9,6 +9,7 @@ QT_LIBINFIX = "E"
> # override variables set by qmake-base to compile Qt/Embedded apps
> #
> export QMAKESPEC = "${STAGING_DATADIR}/${QT_DIR_NAME}/mkspecs/${TARGET_OS}-oe-g++"
> +export OE_QMAKE_QT_CONFIG = "${STAGING_DATADIR}/${QT_DIR_NAME}/mkspecs/qconfig.pri"
> export OE_QMAKE_INCDIR_QT = "${STAGING_INCDIR}/${QT_DIR_NAME}"
> export OE_QMAKE_LIBDIR_QT = "${STAGING_LIBDIR}"
> export OE_QMAKE_LIBS_QT = "qt"
Hi Saul,
Do you have a log of the error you had building qt4-embedded with this
patch?
Regards,
Jonathan
next prev parent reply other threads:[~2013-06-28 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 0:06 [PATCH] qt4e.bbclass: export OE_QMAKE_QT_CONFIG Jonathan Liu
2013-06-28 12:07 ` Jonathan Liu [this message]
2013-06-28 12:28 ` Martin Jansa
2013-06-28 12:40 ` Paul Eggleton
2013-06-28 12:45 ` Martin Jansa
2013-06-28 12:47 ` Paul Eggleton
2013-06-28 12:49 ` Hongxu Jia
2013-06-30 10:34 ` Martin Jansa
2013-06-30 11:44 ` Paul Eggleton
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=51CD7C66.3020702@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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