From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] bluez5_utils: allow install of deprecated tools
Date: Mon, 1 May 2017 16:57:50 +0200 [thread overview]
Message-ID: <20170501165750.1b6c9459@free-electrons.com> (raw)
In-Reply-To: <a98f6fda9cded4f8416b2a6f2249e85be944eca4.1493643541.git.baruch@tkos.co.il>
Hello,
On Mon, 1 May 2017 15:59:41 +0300, Baruch Siach wrote:
> -ifeq ($(BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL),y)
> +ifeq ($(BR2_PACKAGE_BLUEZ5_UTILS_DEPRECATED),y)
> define BLUEZ5_UTILS_INSTALL_GATTTOOL
> $(INSTALL) -D -m 0755 $(@D)/attrib/gatttool $(TARGET_DIR)/usr/bin/gatttool
> endef
> BLUEZ5_UTILS_POST_INSTALL_TARGET_HOOKS += BLUEZ5_UTILS_INSTALL_GATTTOOL
> +BLUEZ5_UTILS_CONF_OPTS += --enable-deprecated
So the --enable-deprecated option only enables the build of gatttool ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-01 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 12:59 [Buildroot] [PATCH 0/4] bluez5_utils: version bump fixes and updates Baruch Siach
2017-05-01 12:59 ` [Buildroot] [PATCH 1/4] bluez5_utils: allow install of deprecated tools Baruch Siach
2017-05-01 14:57 ` Thomas Petazzoni [this message]
2017-05-01 15:09 ` Baruch Siach
2017-05-05 12:32 ` Peter Korsgaard
2017-05-01 12:59 ` [Buildroot] [PATCH 2/4] bluez5_utils: correct the experimental option text Baruch Siach
2017-05-05 12:37 ` Peter Korsgaard
2017-05-01 12:59 ` [Buildroot] [PATCH 3/4] bluez5_utils: allow enabling formerly experimental plugins Baruch Siach
2017-05-05 12:37 ` Peter Korsgaard
2017-05-01 12:59 ` [Buildroot] [PATCH 4/4] bluez5_utils: allow building the midi profile Baruch Siach
2017-05-05 12:37 ` Peter Korsgaard
2017-05-02 15:05 ` [Buildroot] [PATCH 0/4] bluez5_utils: version bump fixes and updates 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=20170501165750.1b6c9459@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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