From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] bluez5_utils: new package
Date: Thu, 3 Apr 2014 22:00:29 +0200 [thread overview]
Message-ID: <20140403220029.450f9b51@skate> (raw)
In-Reply-To: <1396256280-23284-1-git-send-email-marcin@bis.org.pl>
Dear Marcin Bis,
On Mon, 31 Mar 2014 10:58:00 +0200, Marcin Bis wrote:
> This patch adds Bluez 5.x.
> API is not backwards compatible with BlueZ 4.x
... so it is packaged as a separate package.
> BlueZ utils will use systemd and/or udev if enabled.
> Contains a hook for installing GATT support tool, wchich is always
which
> build but not installed by default.
build -> built
> diff --git a/package/bluez5_utils/Config.in b/package/bluez5_utils/Config.in
> new file mode 100644
> index 0000000..809dd8a
> --- /dev/null
> +++ b/package/bluez5_utils/Config.in
> @@ -0,0 +1,54 @@
> +config BR2_PACKAGE_BLUEZ5_UTILS
> + bool "bluez-utils 5.x"
> + depends on !BR2_avr32
> + depends on BR2_USE_WCHAR # libglib2
> + depends on BR2_TOOLCHAIN_HAS_THREADS # dbus, libglib2
> + depends on BR2_USE_MMU # dbus
> + depends on !BR2_PACKAGE_BLUEZ_UTILS # conflicts with 4.x version
> + select BR2_PACKAGE_DBUS
> + select BR2_PACKAGE_LIBGLIB2
> + select BR2_PACKAGE_LIBICAL
> + select BR2_PACKAGE_READLINE
> + help
> + bluez utils version 5.x
> +
> + With this release BlueZ only supports the new Bluetooth Management
> + kernel interface (introduced in Linux 3.4).
Does it need kernel headers >= 3.4 ?
> +# install gatttool (For some reason upstream choose not to do it by default)
> +ifeq ($(BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL),y)
> +define BLUEZ5_UTILS_INSTALL_GATTTOOL
> + $(INSTALL) -D -m 0755 $(@D)/attrib/gatttool $(TARGET_DIR)/usr/bin
The destination path should be a full path, i.e:
$(TARGET_DIR)/usr/bin/gatttool
> +# use udev if available
> +ifeq ($(BR2_PACKAGE_UDEV),y)
You should instead rely on BR2_PACKAGE_HAS_UDEV, so that it works with
both eudev, or the udev built into systemd.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-03 20:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 12:59 [Buildroot] [PATCH] bluez5_utils: new package Marcin Bis
2013-11-04 16:06 ` Thomas De Schampheleire
2013-11-04 21:34 ` [Buildroot] [PATCH v2] " Marcin Bis
2014-03-04 21:38 ` Yann E. MORIN
2014-03-20 13:48 ` [Buildroot] [PATCH v3] " Marcin Bis
2014-03-20 18:21 ` Thomas Petazzoni
2014-03-20 19:28 ` Jerzy Grzegorek
2014-03-21 9:48 ` Marcin Bis
2014-03-21 9:53 ` [Buildroot] [PATCH v4] " Marcin Bis
2014-03-21 11:08 ` Jerzy Grzegorek
2014-03-21 11:42 ` Gustavo Zacarias
2014-03-21 16:45 ` Jerzy Grzegorek
2014-03-21 16:50 ` Gustavo Zacarias
2014-03-23 23:10 ` Jerzy Grzegorek
2014-03-31 8:55 ` Marcin Bis
2014-03-31 8:58 ` [Buildroot] [PATCH v5] " Marcin Bis
2014-04-03 20:00 ` Thomas Petazzoni [this message]
2014-04-04 9:03 ` Marcin Bis
2014-08-02 11:08 ` Thomas Petazzoni
2014-03-21 16:55 ` [Buildroot] [PATCH v4] " Gustavo Zacarias
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=20140403220029.450f9b51@skate \
--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