From: Inga Stotland <inga.stotland@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.von.dentz@intel.com, brian.gix@intel.com,
Inga Stotland <inga.stotland@intel.com>
Subject: [PATCH BlueZ] build: Deprecate meshctl tool
Date: Mon, 3 Oct 2022 16:06:42 -0700 [thread overview]
Message-ID: <20221003230642.164327-1-inga.stotland@intel.com> (raw)
This marks meshctl tool as deprecated since it is not longer
maintained.
---
Makefile.tools | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Makefile.tools b/Makefile.tools
index a99d768dc..4bc355c34 100644
--- a/Makefile.tools
+++ b/Makefile.tools
@@ -348,6 +348,8 @@ man_MANS += tools/rctest.1 tools/l2ping.1 tools/btattach.1 tools/isotest.1
endif
if MESH
+
+if DEPRECATED
bin_PROGRAMS += tools/meshctl
tools_meshctl_SOURCES = tools/meshctl.c \
@@ -372,6 +374,9 @@ tools_meshctl_LDADD = gdbus/libgdbus-internal.la src/libshared-glib.la \
lib/libbluetooth-internal.la \
$(GLIB_LIBS) $(DBUS_LIBS) -ljson-c -lreadline
+EXTRA_DIST += tools/mesh-gatt/local_node.json tools/mesh-gatt/prov_db.json
+endif
+
bin_PROGRAMS += tools/mesh-cfgclient
tools_mesh_cfgclient_SOURCES = tools/mesh-cfgclient.c \
@@ -395,8 +400,6 @@ tools_mesh_cfgtest_LDADD = lib/libbluetooth-internal.la src/libshared-ell.la \
$(ell_ldadd)
endif
-EXTRA_DIST += tools/mesh-gatt/local_node.json tools/mesh-gatt/prov_db.json
-
if DEPRECATED
bin_PROGRAMS += tools/hciattach tools/hciconfig tools/hcitool tools/hcidump \
tools/rfcomm tools/sdptool tools/ciptool
--
2.37.3
next reply other threads:[~2022-10-03 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 23:06 Inga Stotland [this message]
2022-10-04 0:26 ` [BlueZ] build: Deprecate meshctl tool bluez.test.bot
2022-10-04 1:20 ` [PATCH BlueZ] " patchwork-bot+bluetooth
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=20221003230642.164327-1-inga.stotland@intel.com \
--to=inga.stotland@intel.com \
--cc=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
/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