From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] qt: Add option to build and install tools on the target
Date: Tue, 28 Feb 2012 21:09:49 +0000 [thread overview]
Message-ID: <201202282109.49513.arnout@mind.be> (raw)
In-Reply-To: <1330258388-28391-3-git-send-email-ismael.luceno@gmail.com>
On Sunday 26 February 2012 12:13:08 Ismael Luceno wrote:
[snip]
> +config BR2_PACKAGE_QT_TOOLS
> + bool "Compile and install tools"
> + depends on BR2_PACKAGE_QT_SQL_MODULE
> + help
> + If unsure, say N.
The help should specify which tools are included (and maybe also what
they do).
[snip]
> +QT_TARGET_PROGRAMS += qmlviewer
>
> ifeq ($(BR2_PACKAGE_QT_GUI_MODULE),y)
> QT_INSTALL_LIBS += QtGui
> @@ -577,7 +584,12 @@ endef
> 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
> + for i in $(addprefix $(STAGING_DIR)/usr/bin/,$(QT_HOST_PROGRAMS)); do \
> + if [ -x "$$i" ]; then cp "$$i" $(HOST_DIR)/usr/bin; fi; \
> + done
> + for i in $(addprefix $(STAGING_DIR)/usr/bin/,$(QT_TARGET_PROGRAMS)); do \
> + if [ -x "$$i" ]; then cp "$$i" $(TARGET_DIR)/usr/bin; fi; \
> + done
I would remove the checks here. If in some future version these tools
disappear, we want to notice it and update the .mk file accordingly. So
the original mv command should be OK. By the way, if you make such an
additional change (which is unrelated to 'build and install tools on
the target'), it should be mentioned in the commit message.
For the qmlviewer, I assume it is not built if BR2_PACKAGE_QT_TOOLS is
disabled. To support that, you can set
QT_TARGET_PROGRAMS += $(if $(BR2_PACKAGE_QT_TOOLS),qmlviewer))
Or alternatively:
QT_TARGET_PROGRAMS-$(BR2_PACKAGE_QT_TOOLS) += qmlviewer
and use $(QT_TARGET_PROGRAMS-y)
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-02-28 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 12:13 [Buildroot] [PATCH 1/3] qt: remove bogus lines Ismael Luceno
2012-02-26 12:13 ` [Buildroot] [PATCH 2/3] qt: Install QtDeclarative imports Ismael Luceno
2012-02-26 21:28 ` Peter Korsgaard
2012-02-28 20:56 ` Arnout Vandecappelle
2012-02-26 12:13 ` [Buildroot] [PATCH 3/3] qt: Add option to build and install tools on the target Ismael Luceno
2012-02-28 21:09 ` Arnout Vandecappelle [this message]
2012-02-26 21:25 ` [Buildroot] [PATCH 1/3] qt: remove bogus lines Peter Korsgaard
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=201202282109.49513.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox