From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, johan.hedberg@gmail.com, inga.stotland@intel.com
Subject: [PATCH BlueZ v6 14/14] Makefile for meshd
Date: Mon, 9 Jul 2018 11:32:11 -0700 [thread overview]
Message-ID: <20180709183211.16588-15-brian.gix@intel.com> (raw)
In-Reply-To: <20180709183211.16588-1-brian.gix@intel.com>
From: Inga Stotland <inga.stotland@intel.com>
---
Makefile.am | 1 +
Makefile.mesh | 38 ++++++++++++++++++++++++++++++++++++++
2 files changed, 39 insertions(+)
create mode 100644 Makefile.mesh
diff --git a/Makefile.am b/Makefile.am
index 2c9490f5f..0ccf393c6 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -235,6 +235,7 @@ unit_tests =
include Makefile.tools
include Makefile.obexd
include android/Makefile.am
+include Makefile.mesh
if HID2HCI
rulesdir = @UDEV_DIR@/rules.d
diff --git a/Makefile.mesh b/Makefile.mesh
new file mode 100644
index 000000000..29dec6a28
--- /dev/null
+++ b/Makefile.mesh
@@ -0,0 +1,38 @@
+if MESH
+mesh_sources = mesh/mesh.h mesh/mesh.c \
+ mesh/mesh-io.h mesh/mesh-io.c \
+ mesh/mesh-io-api.h mesh/bt.h \
+ mesh/mesh-io-generic.h \
+ mesh/mesh-io-generic.c \
+ mesh/hci.h mesh/hci.c \
+ mesh/storage.h mesh/storage.c \
+ mesh/net.h mesh/net.c \
+ mesh/display.h mesh/display.c \
+ mesh/crypto.h mesh/crypto.c \
+ mesh/friend.h mesh/friend.c \
+ mesh/appkeys.h mesh/appkey.c \
+ mesh/node.h mesh/node.c \
+ mesh/prov.h mesh/prov.c \
+ mesh/provision.h mesh/provision.c \
+ mesh/model.h mesh/model.c \
+ mesh/cfgmod.h mesh/cfgmod-server.c \
+ mesh/mesh-db.h mesh/mesh-db.c \
+ mesh/util.h mesh/util.c \
+ mesh/mesh-defs.h
+libexec_PROGRAMS += mesh/meshd
+
+mesh_meshd_SOURCES = $(mesh_sources) mesh/main.c
+
+mesh_meshd_LDADD = src/shared/ecc.lo @DBUS_LIBS@ @ELL_LIBS@ -ljson-c
+
+noinst_PROGRAMS += mesh/btmesh
+
+mesh_btmesh_SOURCES = $(mesh_sources) \
+ mesh/agent.h \
+ mesh/agent.c \
+ mesh/btmesh.c
+
+mesh_btmesh_LDADD = src/shared/ecc.lo src/libshared-mainloop.la \
+ -lreadline @ELL_LIBS@ -ljson-c
+
+endif
--
2.14.4
prev parent reply other threads:[~2018-07-09 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 18:31 [PATCH BlueZ v6 00/14] Bluetooth Mesh Daemon Brian Gix
2018-07-09 18:31 ` [PATCH BlueZ v6 01/14] mesh: Shared private meshd interfaces Brian Gix
2018-07-09 18:31 ` [PATCH BlueZ v6 02/14] mesh: Mesh crypto support Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 03/14] mesh: Infrastructure for Mesh daemon Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 04/14] mesh: Initial Mesh Friendship support Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 05/14] mesh: Provisioning logic for mesh Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 06/14] mesh: Upper and Lower mesh transport Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 07/14] mesh: Add Accessors to Transport layer data Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 08/14] mesh: Header files for mesh access layer and utilities Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 09/14] mesh: Source " Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 10/14] mesh: Source code for handling access layer mux/demux Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 11/14] mesh: Mesh config server model Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 12/14] mesh: Read and write mesh configuration in JSON format Brian Gix
2018-07-09 18:32 ` [PATCH BlueZ v6 13/14] mesh: Sample device composition " Brian Gix
2018-07-09 18:32 ` Brian Gix [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=20180709183211.16588-15-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).