From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch for-2011.05/more-qt-fixes
Date: Sun, 3 Apr 2011 17:18:59 +0200 [thread overview]
Message-ID: <cover.1301843856.git.thomas.petazzoni@free-electrons.com> (raw)
Hello,
Changes since the previous version:
* Pass MAKEFLAGS down to Qt ./configure script, in addition to the
-j$(BR2_JLEVEL) flag.
* Test if the usr/lib/qt/plugins exists in STAGING_DIR before copying
its contents to the TARGET_DIR. It is a bit pedantic as the current
version of Qt, with just QtCore and no other libraries or plugins
installs one plugin, but it may not be the case in future versions
of Qt.
The following changes since commit 4bc1041db6ce805a8d96f653e50ce06eb6849d4b:
lighttpd: fix build without webdav support (2011-04-02 10:24:59 +0200)
are available in the git repository at:
git://git.busybox.net/~tpetazzoni/git/buildroot for-2011.05/more-qt-fixes
Thomas Petazzoni (2):
qt: fix plugin installation and change plugin path
qt: speed up qmake build
package/qt/qt-4.7.2-configure.patch | 48 +++++++++++++++++++++++++++++++++++
package/qt/qt.mk | 17 +++++-------
2 files changed, 55 insertions(+), 10 deletions(-)
create mode 100644 package/qt/qt-4.7.2-configure.patch
Thanks,
--
Thomas Petazzoni
next reply other threads:[~2011-04-03 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 15:18 Thomas Petazzoni [this message]
2011-04-03 15:19 ` [Buildroot] [PATCH 1/2] qt: fix plugin installation and change plugin path Thomas Petazzoni
2011-04-03 15:19 ` [Buildroot] [PATCH 2/2] qt: speed up qmake build Thomas Petazzoni
2011-04-03 18:55 ` [Buildroot] [pull request] Pull request for branch for-2011.05/more-qt-fixes Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2011-04-02 16:52 Thomas Petazzoni
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.1301843856.git.thomas.petazzoni@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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