From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/bluez5_utils: Allow user to enable disabled plugins
Date: Tue, 21 Mar 2017 18:01:09 +0100 [thread overview]
Message-ID: <874lymlg2y.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170321160237.31058-1-andriy.shevchenko@linux.intel.com> (Andy Shevchenko's message of "Tue, 21 Mar 2017 18:02:35 +0200")
>>>>> "Andy" == Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
> Disregard to increase just minor version BlueZ 5.44 is drastically different in
> a way what tools and plugins are enabled and installed by default.
> Extend Buildroot package to cover these changes.
> Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> package/bluez5_utils/Config.in | 28 +++++++++++++++++++++++++++-
> package/bluez5_utils/bluez5_utils.mk | 36 ++++++++++++++++++++++++++++++++++++
> 2 files changed, 63 insertions(+), 1 deletion(-)
> diff --git a/package/bluez5_utils/Config.in b/package/bluez5_utils/Config.in
> index a7c0ee4ba..e99f0f69f 100644
> --- a/package/bluez5_utils/Config.in
> +++ b/package/bluez5_utils/Config.in
> @@ -48,6 +48,11 @@ config BR2_PACKAGE_BLUEZ5_UTILS_CLIENT
> comment "bluez5-utils client needs a glibc or musl toolchain"
> depends on BR2_TOOLCHAIN_USES_UCLIBC
> +config BR2_PACKAGE_BLUEZ5_UTILS_DEPRECATED
> + bool "build deprecated tools"
> + help
> + Build BlueZ 5.x deprecated tools (hciattach, gatttool, ...).
> +
> config BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL
> bool "install GATT tool"
> depends on BR2_PACKAGE_BLUEZ5_UTILS_CLIENT
Then _UTILS_GATTTOOL should depend on _UTILS_DEPRECATED. Or perhaps it
doesn't make sense to have a dedicated option for this and it should
just be automatically installed when deprecated is enabled.
It would also be good to add the autobuilder failures:
http://autobuild.buildroot.net/?reason=bluez5_utils-5.44
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-03-21 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:02 [Buildroot] [PATCH v2] package/bluez5_utils: Allow user to enable disabled plugins Andy Shevchenko
2017-03-21 16:02 ` [Buildroot] [PATCH v2] package/uclibc: Enable wordexp functionality Andy Shevchenko
2017-03-21 16:06 ` Thomas Petazzoni
2017-03-21 16:11 ` Andy Shevchenko
2017-03-21 16:17 ` Thomas Petazzoni
2017-03-21 16:23 ` Andy Shevchenko
2017-03-21 16:28 ` Baruch Siach
2017-04-09 4:32 ` Waldemar Brodkorb
2017-04-09 7:42 ` Thomas Petazzoni
2017-03-21 19:53 ` Waldemar Brodkorb
2017-04-16 14:29 ` Waldemar Brodkorb
2017-04-29 12:26 ` Thomas Petazzoni
2017-03-21 16:02 ` [Buildroot] [PATCH v2] Revert "bluez5_utils: not available with uClibc" Andy Shevchenko
2017-03-21 17:01 ` Peter Korsgaard [this message]
2017-03-21 17:06 ` [Buildroot] [PATCH v2] package/bluez5_utils: Allow user to enable disabled plugins Andy Shevchenko
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=874lymlg2y.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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