From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] bluez5_utils: add ability to build sixaxis plugin
Date: Sat, 18 Jul 2015 22:54:47 +0200 [thread overview]
Message-ID: <20150718225447.3807a4e0@free-electrons.com> (raw)
In-Reply-To: <1437036374-4179-1-git-send-email-limpens@gmail.com>
Dear Eric Limpens,
On Thu, 16 Jul 2015 10:46:14 +0200, Eric Limpens wrote:
> +config BR2_PACKAGE_BLUEZ5_PLUGINS_SIXAXIS
> + bool "build sixaxis plugin"
> + help
> + Build BlueZ 5.x sixaxis plugin (support Sony Dualshock controller)
In fact, the sixaxis plugin can only be enabled when udev support is
available:
AM_CONDITIONAL(SIXAXIS, test "${enable_sixaxis}" = "yes" &&
test "${enable_udev}" != "no")
So I've adjusted the Config.in description of the option to describe
this udev dependency, and applied your patch.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-18 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 8:46 [Buildroot] [PATCH 1/1] bluez5_utils: add ability to build sixaxis plugin Eric Limpens
2015-07-18 20:54 ` Thomas Petazzoni [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=20150718225447.3807a4e0@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