From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] bluez: Make it possible to deselect USB support
Date: Mon, 4 Mar 2013 17:40:53 +0100 [thread overview]
Message-ID: <20130304164053.GW5360@pengutronix.de> (raw)
In-Reply-To: <1362143647-32743-1-git-send-email-bernhard@bwalle.de>
On Fri, Mar 01, 2013 at 02:14:07PM +0100, Bernhard Walle wrote:
> When using a Bluetooth module that is not connected with USB, it makes
> sense to deselect support for it. This saves building libusb and
> libusb-compat.
>
tnx, applied
Michael
> Signed-off-by: Bernhard Walle <bernhard@bwalle.de>
> ---
> rules/bluez.in | 9 ++++++++-
> rules/bluez.make | 2 +-
> 2 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/rules/bluez.in b/rules/bluez.in
> index 474c434..cf489a4 100644
> --- a/rules/bluez.in
> +++ b/rules/bluez.in
> @@ -4,7 +4,7 @@ menuconfig BLUEZ
> tristate "bluez "
> select DBUS
> select GLIB
> - select LIBUSB_COMPAT
> + select LIBUSB_COMPAT if BLUEZ_USB
> select ALSA_LIB if BLUEZ_ALSA
> select GSTREAMER if BLUEZ_GSTREAMER
> select GST_PLUGINS_BASE if BLUEZ_GSTREAMER
> @@ -21,6 +21,13 @@ config BLUEZ_SYSTEMD_UNIT
> depends on SYSTEMD
> prompt "install systemd unit files for bluez"
>
> +config BLUEZ_USB
> + bool "USB support"
> + default y
> + help
> + Build bluez with USB support. Only disable this if your Bluetooth
> + adapter is not connected via USB (for example with an UART or SDIO).
> +
> config BLUEZ_ALSA
> bool "alsa support"
> help
> diff --git a/rules/bluez.make b/rules/bluez.make
> index 848b99f..9bfd4df 100644
> --- a/rules/bluez.make
> +++ b/rules/bluez.make
> @@ -52,7 +52,7 @@ BLUEZ_CONF_OPT := $(CROSS_AUTOCONF_USR) \
> --disable-gatt-example \
> --$(call ptx/endis, PTXCONF_BLUEZ_GSTREAMER)-gstreamer \
> --$(call ptx/endis, PTXCONF_BLUEZ_ALSA)-alsa \
> - --enable-usb \
> + --$(call ptx/endis, PTXCONF_BLUEZ_USB)-usb \
> --disable-tracer \
> --enable-tools \
> --enable-bccmd \
> --
> 1.8.1.4
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-03-04 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 13:14 Bernhard Walle
2013-03-04 16:40 ` Michael Olbrich [this message]
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=20130304164053.GW5360@pengutronix.de \
--to=m.olbrich@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