From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] qt: Add option to build and install tools on the target
Date: Sun, 4 Mar 2012 16:13:47 +0100 [thread overview]
Message-ID: <201203041613.48008.arnout@mind.be> (raw)
In-Reply-To: <1330830287-1502-1-git-send-email-ismael.luceno@gmail.com>
On Sunday 04 March 2012 04:04:47 Ismael Luceno wrote:
>
> Signed-off-by: Ismael Luceno <ismael.luceno@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
A few comments below, but nothing critical.
> ---
> package/qt/Config.in | 23 +++++++++++++++++++++++
> package/qt/qt.mk | 10 ++++++++++
> 2 files changed, 33 insertions(+), 0 deletions(-)
>
> diff --git a/package/qt/Config.in b/package/qt/Config.in
> index 3a552d0..e2c7400 100644
> --- a/package/qt/Config.in
> +++ b/package/qt/Config.in
> @@ -16,6 +16,29 @@ config BR2_PACKAGE_QT_DEBUG
> help
> If unsure, say N.
>
> +menuconfig BR2_PACKAGE_QT_TOOLS
> + bool "Compile and install tools"
> + depends on BR2_PACKAGE_QT_SQL_MODULE && BR2_PACKAGE_QT_GUI_MODULE
This is annoying... SQL is only needed for assistant and designer, not
for qtconfig or qmlplugindump. Is there a possibility to tell qt to just
build the selected tools? That probably requires hacking
tools/tools.pro...
Maybe add to the help text of the comment, that sql isn't actually
needed except for building.
> +
> +if BR2_PACKAGE_QT_TOOLS
> +
> +config BR2_PACKAGE_QT_TOOLS_QTCONFIG
> + bool "qtconfig"
> + depends on BR2_PACKAGE_QT_GUI_X11
Doesn't qtconfig work in qws?
[snip]
> @@ -514,6 +520,9 @@ endef
>
> QT_INSTALL_LIBS += QtCore
> QT_HOST_PROGRAMS += moc rcc qmake lrelease
> +QT_TARGET_PROGRAMS += $(if $(BR2_PACKAGE_QT_TOOLS_QTCONFIG),qtconfig) \
> + $(if $(BR2_PACKAGE_QT_TOOLS_QMLVIEWER),qmlviewer) \
> + $(if $(BR2_PACKAGE_QT_TOOLS_QMLPLUGINDUMP),qmlplugindump)
Personally, I prefer the
QT_TARGET_PROGRAMS-$(BR2_PACKAGE_QT_TOOLS_QTCONFIG) += qtconfig
approach, but that's a matter of taste I guess.
>
> ifeq ($(BR2_PACKAGE_QT_GUI_MODULE),y)
> QT_INSTALL_LIBS += QtGui
> @@ -583,6 +592,7 @@ define QT_INSTALL_STAGING_CMDS
> $(MAKE) -C $(@D) install
> mkdir -p $(HOST_DIR)/usr/bin
> mv $(addprefix $(STAGING_DIR)/usr/bin/,$(QT_HOST_PROGRAMS)) $(HOST_DIR)/usr/bin
> + mv $(addprefix $(STAGING_DIR)/usr/bin/,$(QT_TARGET_PROGRAMS)) $(TARGET_DIR)/usr/bin
(so that would mean putting $(QT_TARGET_PROGRAMS-y) here)
> rm -rf $(HOST_DIR)/usr/mkspecs
> mv $(STAGING_DIR)/usr/mkspecs $(HOST_DIR)/usr
> $(QT_INSTALL_QT_CONF)
>
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-04 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 3:04 [Buildroot] [PATCHv2] qt: Add option to build and install tools on the target Ismael Luceno
2012-03-04 15:13 ` Arnout Vandecappelle [this message]
2012-03-04 19:03 ` Ismael Luceno
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=201203041613.48008.arnout@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.