From: Martin Jansa <martin.jansa@gmail.com>
To: Wills Wang <wills.wang.open@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qt4e: override variables OE_QMAKE_QT_CONFIG
Date: Sat, 29 Jun 2013 14:15:36 +0200 [thread overview]
Message-ID: <20130629121536.GS3261@jama> (raw)
In-Reply-To: <CAC6FaqyHsqMPbvZa=gO4S8E+_ZyckNAvqe+X_O5cdJH5uYxexg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
On Sat, Jun 29, 2013 at 08:12:51PM +0800, Wills Wang wrote:
> override variables OE_QMAKE_QT_CONFIG to compile Qt/Embedded apps
Thanks for forwarding it, btw it has extra line breaks, are you using
git send-email?
> diff --git a/meta/classes/qt4e.bbclass b/meta/classes/qt4e.bbclass
> index de2a68d..13b1050 100755
> --- 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"
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-06-29 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC6FaqyMxgZP4ODaZiACA8qPBCNRZUAg=UV_WufTqe1hZkdUdw@mail.gmail.com>
2013-06-29 12:12 ` [PATCH] qt4e: override variables OE_QMAKE_QT_CONFIG Wills Wang
2013-06-29 12:15 ` Martin Jansa [this message]
2013-06-29 12:19 ` [PATCHv2] " Martin Jansa
2013-07-03 9:43 ` Jonathan Liu
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=20130629121536.GS3261@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wills.wang.open@gmail.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