Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Limpens <limpens@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] bluez5_utils: add ability to build sixaxis plugin
Date: Thu, 16 Jul 2015 10:46:14 +0200	[thread overview]
Message-ID: <1437036374-4179-1-git-send-email-limpens@gmail.com> (raw)

Signed-off-by: Eric Limpens <limpens@gmail.com>
---
 package/bluez5_utils/Config.in       | 5 +++++
 package/bluez5_utils/bluez5_utils.mk | 7 +++++++
 2 files changed, 12 insertions(+)

diff --git a/package/bluez5_utils/Config.in b/package/bluez5_utils/Config.in
index 472432b..dade0ee 100644
--- a/package/bluez5_utils/Config.in
+++ b/package/bluez5_utils/Config.in
@@ -58,6 +58,11 @@ config BR2_PACKAGE_BLUEZ5_UTILS_EXPERIMENTAL
 	help
 	  Build BlueZ 5.x experimental plugins (SAP, NFC, ...).
 
+config BR2_PACKAGE_BLUEZ5_PLUGINS_SIXAXIS
+	bool "build sixaxis plugin"
+	help
+	  Build BlueZ 5.x sixaxis plugin (support Sony Dualshock controller)
+
 config BR2_PACKAGE_BLUEZ5_UTILS_TEST
 	bool "build tests"
 	help
diff --git a/package/bluez5_utils/bluez5_utils.mk b/package/bluez5_utils/bluez5_utils.mk
index a1adbe1..4c50e53 100644
--- a/package/bluez5_utils/bluez5_utils.mk
+++ b/package/bluez5_utils/bluez5_utils.mk
@@ -41,6 +41,13 @@ else
 BLUEZ5_UTILS_CONF_OPTS += --disable-experimental
 endif
 
+# enable sixaxis plugin
+ifeq ($(BR2_PACKAGE_BLUEZ5_PLUGINS_SIXAXIS),y)
+BLUEZ5_UTILS_CONF_OPTS += --enable-sixaxis
+else
+BLUEZ5_UTILS_CONF_OPTS += --disable-sixaxis
+endif
+
 # 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
-- 
1.9.1

             reply	other threads:[~2015-07-16  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  8:46 Eric Limpens [this message]
2015-07-18 20:54 ` [Buildroot] [PATCH 1/1] bluez5_utils: add ability to build sixaxis plugin Thomas Petazzoni

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=1437036374-4179-1-git-send-email-limpens@gmail.com \
    --to=limpens@gmail.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