From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <r.hieber@pengutronix.de>
Subject: [ptxdist] [PATCH v2 3/5] bluez: make it possible to disable building the tools
Date: Mon, 12 Nov 2018 15:56:38 +0100 [thread overview]
Message-ID: <20181112145640.22901-4-r.hieber@pengutronix.de> (raw)
In-Reply-To: <20181112145640.22901-1-r.hieber@pengutronix.de>
Until now, PTXCONF_BLUEZ_UTILS only had an effect on which tools were
installed in the targetinstall stage, but it can also be used to disable
the respective configure options in the prepare stage so the tools are
only built when needed.
Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
---
rules/bluez.make | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rules/bluez.make b/rules/bluez.make
index 3ca8b9cb7..b161d2730 100644
--- a/rules/bluez.make
+++ b/rules/bluez.make
@@ -43,8 +43,8 @@ BLUEZ_CONF_OPT := $(CROSS_AUTOCONF_USR) \
--enable-threads \
--enable-library \
--$(call ptx/endis, PTXCONF_BLUEZ_INSTALL_TESTSCRIPTS)-test \
- --enable-tools \
- --enable-monitor \
+ --$(call ptx/endis, PTXCONF_BLUEZ_UTILS)-tools \
+ --$(call ptx/endis, PTXCONF_BLUEZ_UTILS)-monitor \
--enable-udev \
--disable-cups \
--disable-obex \
--
2.19.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-11-12 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 14:56 [ptxdist] [PATCH v2 0/5] bluez fixes and version bump to 5.50 Roland Hieber
2018-11-12 14:56 ` [ptxdist] [PATCH v2 1/5] bluez: fix license string Roland Hieber
2018-11-12 14:56 ` [ptxdist] [PATCH v2 2/5] bluez: consistently make use of $(ptx/nl) Roland Hieber
2018-11-12 14:56 ` Roland Hieber [this message]
2018-11-12 14:56 ` [ptxdist] [PATCH v2 4/5] bluez: rename PTXCONF_BLUEZ{_UTILS -> _TOOLS}* for consistency Roland Hieber
2018-11-12 14:56 ` [ptxdist] [PATCH v2 5/5] bluez: version bump 5.30 -> 5.50 Roland Hieber
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=20181112145640.22901-4-r.hieber@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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