linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, inga.stotland@intel.com
Subject: [PATCH BlueZ] build: Include dependancies for ell/settings.[ch]
Date: Wed,  4 Dec 2019 11:15:16 -0800	[thread overview]
Message-ID: <20191204191516.13178-1-brian.gix@intel.com> (raw)

Including settings.[ch] in a build requires the following chained
dependancies:
PEM
CERT
KEY
PKSC5
BASE64
---
 Makefile.am | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/Makefile.am b/Makefile.am
index 8d419fb30..836a4fcd2 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -121,12 +121,22 @@ ell_headers = ell/util.h \
 			ell/io.h \
 			ell/idle.h \
 			ell/main.h \
+			ell/settings.h \
 			ell/strv.h \
 			ell/string.h \
 			ell/utf8.h \
 			ell/dbus.h \
 			ell/dbus-service.h \
-			ell/dbus-client.h
+			ell/dbus-client.h \
+			ell/key.h \
+			ell/cert.h \
+			ell/pem.h \
+			ell/base64.h \
+			ell/pkcs5.h \
+			ell/asn1-private.h \
+			ell/pkcs5-private.h \
+			ell/cert-private.h \
+			ell/pem-private.h
 
 ell_sources = ell/private.h ell/missing.h \
 			ell/util.c \
@@ -139,10 +149,16 @@ ell_sources = ell/private.h ell/missing.h \
 			ell/io.c \
 			ell/idle.c \
 			ell/main.c \
+			ell/settings.c \
 			ell/strv.c \
 			ell/string.c \
 			ell/cipher.c \
 			ell/checksum.c \
+			ell/pem.c \
+			ell/cert.c \
+			ell/key.c \
+			ell/pkcs5.c \
+			ell/base64.c \
 			ell/utf8.c \
 			ell/dbus-private.h \
 			ell/dbus.c \
-- 
2.21.0


             reply	other threads:[~2019-12-04 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 19:15 Brian Gix [this message]
2019-12-05  0:28 ` [PATCH BlueZ] build: Include dependancies for ell/settings.[ch] Gix, Brian

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=20191204191516.13178-1-brian.gix@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@intel.com \
    --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).