From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] bluez5_utils: new package
Date: Sat, 2 Aug 2014 13:08:02 +0200 [thread overview]
Message-ID: <20140802130802.26bd0121@free-electrons.com> (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
>
> BlueZ utils will use systemd and/or udev if enabled.
> Contains a hook for installing GATT support tool, wchich is always
> build but not installed by default.
>
> Signed-off-by: Marcin Bis <marcin@bis.org.pl>
> ---
> package/Config.in | 1 +
> package/bluez5_utils/Config.in | 54 ++++++++++++++++++++++++++++++++++
> package/bluez5_utils/bluez5_utils.mk | 54 ++++++++++++++++++++++++++++++++++
> 3 files changed, 109 insertions(+)
> create mode 100644 package/bluez5_utils/Config.in
> create mode 100644 package/bluez5_utils/bluez5_utils.mk
I've applied your patch, after making a number of changes:
[Thomas:
- Add dependency on 3.4 kernel headers
- Add options for OBEX support and client support, to make the
libical and readline dependencies optional.
- Rewrap Config.in help text.
- Adapt indentation in .mk file.
- Bump to version 5.21.
- Use BR2_PACKAGE_HAS_UDEV instead of BR2_PACKAGE_UDEV.]
It would be great if you could test the latest master and confirm that
it works for you.
Thanks a lot for this contribution!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-02 11:08 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
2014-04-04 9:03 ` Marcin Bis
2014-08-02 11:08 ` Thomas Petazzoni [this message]
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=20140802130802.26bd0121@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