From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 3/4] bluez/pre-build: installing the test scripts needs the source tree
Date: Thu, 23 Jan 2014 10:52:44 +0100 [thread overview]
Message-ID: <1390470765-9417-4-git-send-email-jbe@pengutronix.de> (raw)
In-Reply-To: <1390470765-9417-1-git-send-email-jbe@pengutronix.de>
When installing the test scripts, this package cannot be used in its
pre-build archive form. But else it can. So disable this feature only
on demand.
Signed-off-by: Juergen Beisert <jbe@pengutronix.de>
---
rules/bluez.make | 3 +++
1 file changed, 3 insertions(+)
diff --git a/rules/bluez.make b/rules/bluez.make
index 9bfd4df..b46bece 100644
--- a/rules/bluez.make
+++ b/rules/bluez.make
@@ -24,6 +24,9 @@ BLUEZ_URL := $(call ptx/mirror, KERNEL, bluetooth/$(BLUEZ).$(BLUEZ_SUFFIX))
BLUEZ_SOURCE := $(SRCDIR)/$(BLUEZ).$(BLUEZ_SUFFIX)
BLUEZ_DIR := $(BUILDDIR)/$(BLUEZ)
BLUEZ_LICENSE := GPLv2+ LGPLv2.1+
+ifdef PTXCONF_BLUEZ_INSTALL_TESTSCRIPTS
+BLUEZ_DEVPKG := NO
+endif
# the tools don't depend on the generated headers
BLUEZ_MAKE_PAR := NO
--
1.8.5.2
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-23 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 9:52 [ptxdist] [PATCH] Fix some packages in regard to PTXdist's pre-build archive feature Juergen Beisert
2014-01-23 9:52 ` [ptxdist] [PATCH 1/4] QT4/pre-build: installing the examples needs the source tree Juergen Beisert
2014-01-23 10:57 ` Marc Kleine-Budde
2014-01-23 11:38 ` Juergen Beisert
2014-01-23 9:52 ` [ptxdist] [PATCH 2/4] Mono/pre-build: targetinstall needs access to " Juergen Beisert
2014-01-23 9:52 ` Juergen Beisert [this message]
2014-01-23 9:52 ` [ptxdist] [PATCH 4/4] PTXdist: be more helpful using the pre-build archive feature Juergen Beisert
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=1390470765-9417-4-git-send-email-jbe@pengutronix.de \
--to=jbe@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