From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Qt4 qmake & other fixes
Date: Sun, 26 Feb 2012 22:27:39 +0000 [thread overview]
Message-ID: <cover.1330294151.git.paul.eggleton@linux.intel.com> (raw)
This patchset enables building qmake for the target with other target
utilities. I also fixed a couple of build failures in the process.
In addition I've used the same method to build qmake in the
qt4-tools-nativesdk recipe. This wasn't strictly necessary, however I
think it would be good to be consistent and incidentally the resulting
qmake executable is slightly smaller.
Since the RFC version, a few issues were fixed:
* Ensure the qmake changes work when the platform is different e.g.
linux-gnueabi-oe-g++ instead of linux-oe-g++
* Install an appropriate environment setup script adapted from the
former separate qmake2 recipe
* Fix the gcc 4.6 error by fixing the root cause (inability to correctly
detect the C++ compiler as g++) rather than hacking around it.
* Format some of the patches so they can be used with git am
Thanks to Philip Balister for helping me test the qmake improvements.
The following changes since commit 30253358f5e76fb7b25be27198b4c125e0dbdf2c:
Quoting fixes (2012-02-26 12:50:36 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/qmake-target
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/qmake-target
Paul Eggleton (4):
qt4: fix compile error in Qt 4.8.0 with gcc 4.6
qt4: build qmake for the target
qt4-tools-nativesdk: fix build of 4.7.4
qt4-tools-nativesdk: improve and tidy up qmake build
meta/recipes-qt/qt4/files/qmake-exists-check.patch | 19 -------
meta/recipes-qt/qt4/files/target_qmake.patch | 16 ++++++
meta/recipes-qt/qt4/qt-4.7.4.inc | 11 +----
meta/recipes-qt/qt4/qt-4.8.0.inc | 13 +----
.../qt4/qt-4.8.0/configure_oe_compiler.patch | 31 ++++++++++++
meta/recipes-qt/qt4/qt-4.8.0/qmake_pri_fixes.patch | 51 ++++++++++++++++++++
meta/recipes-qt/qt4/qt4-embedded_4.7.4.bb | 2 +-
meta/recipes-qt/qt4/qt4-embedded_4.8.0.bb | 2 +-
meta/recipes-qt/qt4/qt4-tools-nativesdk.inc | 29 +++++++----
meta/recipes-qt/qt4/qt4-tools-nativesdk_4.8.0.bb | 2 +
meta/recipes-qt/qt4/qt4-x11-free_4.7.4.bb | 2 +-
meta/recipes-qt/qt4/qt4.inc | 47 ++++++++++++++++--
12 files changed, 168 insertions(+), 57 deletions(-)
delete mode 100644 meta/recipes-qt/qt4/files/qmake-exists-check.patch
create mode 100644 meta/recipes-qt/qt4/files/target_qmake.patch
create mode 100644 meta/recipes-qt/qt4/qt-4.8.0/configure_oe_compiler.patch
create mode 100644 meta/recipes-qt/qt4/qt-4.8.0/qmake_pri_fixes.patch
--
1.7.5.4
next reply other threads:[~2012-02-26 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 22:27 Paul Eggleton [this message]
2012-02-26 22:27 ` [PATCH 1/4] qt4: fix compile error in Qt 4.8.0 with gcc 4.6 Paul Eggleton
2012-02-26 22:55 ` Koen Kooi
2012-02-26 22:59 ` Paul Eggleton
2012-02-26 23:05 ` Koen Kooi
2012-02-27 0:32 ` Paul Eggleton
2012-02-26 22:27 ` [PATCH 2/4] qt4: build qmake for the target Paul Eggleton
2012-02-26 22:27 ` [PATCH 3/4] qt4-tools-nativesdk: fix build of 4.7.4 Paul Eggleton
2012-02-26 22:27 ` [PATCH 4/4] qt4-tools-nativesdk: improve and tidy up qmake build 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=cover.1330294151.git.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