From: Sonny Sasaka <sonnysasaka@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: Sonny Sasaka <sonnysasaka@chromium.org>
Subject: [PATCH v2] build: Add an option to explicitly enable hid2hci
Date: Wed, 13 May 2020 14:38:12 -0700 [thread overview]
Message-ID: <20200513213812.23165-1-sonnysasaka@chromium.org> (raw)
In-Reply-To: <77B1AB20-C903-427C-A3BD-E10C79815EF9@holtmann.org>
hid2hci is no longer a common use. This patch changes the default to not
build and install hid2hci and provide a configure flag --enable-hid2hci
to explicitly enable it.
---
configure.ac | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 1433ace4a..e1c8fd9ad 100644
--- a/configure.ac
+++ b/configure.ac
@@ -218,7 +218,9 @@ if (test "${enable_udev}" != "no" && test -z "${path_udevdir}"); then
fi
AC_SUBST(UDEV_DIR, [${path_udevdir}])
-AM_CONDITIONAL(HID2HCI, test "${enable_tools}" != "no" &&
+AC_ARG_ENABLE(hid2hci, AC_HELP_STRING([--enable-hid2hci],
+ [enable hid2hci tool]), [enable_hid2hci=${enableval}])
+AM_CONDITIONAL(HID2HCI, test "${enable_hid2hci}" = "yes" &&
test "${enable_udev}" != "no")
AC_ARG_ENABLE(cups, AC_HELP_STRING([--disable-cups],
--
2.17.1
next prev parent reply other threads:[~2020-05-13 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 0:55 [PATCH] build: Add an option to explicitly disable installing hid2hci Sonny Sasaka
2020-05-06 11:06 ` Marcel Holtmann
2020-05-06 17:05 ` Sonny Sasaka
2020-05-12 21:19 ` Sonny Sasaka
2020-05-13 8:02 ` Marcel Holtmann
2020-05-13 21:38 ` Sonny Sasaka [this message]
2020-05-18 7:53 ` [PATCH v2] build: Add an option to explicitly enable hid2hci Marcel Holtmann
2020-05-13 21:41 ` [PATCH] build: Add an option to explicitly disable installing hid2hci Sonny Sasaka
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=20200513213812.23165-1-sonnysasaka@chromium.org \
--to=sonnysasaka@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).