Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bluez5_utils: fix build of gatttool
Date: Mon, 1 May 2017 10:38:56 +0300	[thread overview]
Message-ID: <20170501073856.cgnhegilk7dqvg3v@tarshish> (raw)
In-Reply-To: <20170501092142.216bc5b9@free-electrons.com>

Hi Thomas,

On Mon, May 01, 2017 at 09:21:42AM +0200, Thomas Petazzoni wrote:
> On Mon,  1 May 2017 09:28:27 +0300, Baruch Siach wrote:
> > Since BlueZ 5.44 gatttool is hidden behind the --enable-deprecated configure
> > option.
> > 
> > Also, update the help text with the new status of gatttool.
> > 
> > Fixes:
> > http://autobuild.buildroot.net/results/ddb/ddb975c9e1475fee1da63cb21240d8d59b161076/
> > http://autobuild.buildroot.net/results/19a/19adc0aa5a7e48119ef4ba25ba0403867f74f678/
> > http://autobuild.buildroot.net/results/9bd/9bd8e13ddffdd0631ddca30ec40cc4664729b0cb/
> > 
> > Cc: Marcin Bis <marcin@bis.org.pl>
> > Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> 
> We have lots of patches pending on bluez5_utils, to solve this issue
> and others. It's not clear what is the overall plan, as all the patches
> have been sent separately (i.e not in a series).
> 
> See
> https://patchwork.ozlabs.org/project/buildroot/list/?submitter=&state=&q=bluez&archive=&delegate=.
> 
> Essentially, your patch is the third one to solve the gattool problem.

This patch is essentially equivalent to that of Bernd[1], expect that is also 
updates the help text.

I think Andy's suggestion[2] is better than both, but it needs some more work 
to address Peter's comments, and maybe split into separate tools and plugins 
patches. I also think that we should group all deprecated tools together, and 
replace the BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL option with 
BR2_PACKAGE_BLUEZ5_UTILS_DEPRECATED.

I don't think we should remove gatttool installation as Sam suggests[3]. E.g. 
the hciattach tool is also deprecated upstream, but it is unfortunately still 
required for many real world Bluetooth installations.

I'll take over Andy's patch as time permits.

[1] https://patchwork.ozlabs.org/patch/736377/

[2] https://patchwork.ozlabs.org/patch/741645/

[3] https://patchwork.ozlabs.org/patch/748801/

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

      reply	other threads:[~2017-05-01  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01  6:28 [Buildroot] [PATCH] bluez5_utils: fix build of gatttool Baruch Siach
2017-05-01  7:21 ` Thomas Petazzoni
2017-05-01  7:38   ` Baruch Siach [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=20170501073856.cgnhegilk7dqvg3v@tarshish \
    --to=baruch@tkos.co.il \
    --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