From: Jan Kiszka <jan.kiszka@siemens.com>
To: Xenomai <xenomai@lists.linux.dev>
Cc: Aaron Marcher <aaron@sigma-star.at>
Subject: [PATCH] lib/copperplate: Add libfuse if building with registry support
Date: Sat, 22 Apr 2023 11:53:23 +0200 [thread overview]
Message-ID: <f18bffbd-362d-8acb-2b37-9ac1f7cd4d15@siemens.com> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
While our userspace tools gain libfuse via XENO_USER_APP_LDFLAGS if the
registry is enabled, libcopperplate itself does not if it includes
libregistry. Fix that.
Suggested-by: Aaron Marcher <aaron@sigma-star.at>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
lib/copperplate/Makefile.am | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/copperplate/Makefile.am b/lib/copperplate/Makefile.am
index c6edea9853..0dd52c7367 100644
--- a/lib/copperplate/Makefile.am
+++ b/lib/copperplate/Makefile.am
@@ -34,6 +34,9 @@ libregistry_la_SOURCES = registry.c
libregistry_la_CPPFLAGS = \
$(libcopperplate@CORE@_la_CPPFLAGS) \
@XENO_FUSE_CFLAGS@
+
+libregistry_la_LIBADD = \
+ @FUSE_LIBS@
endif
if XENO_PSHARED
--
2.35.3
reply other threads:[~2023-04-22 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f18bffbd-362d-8acb-2b37-9ac1f7cd4d15@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aaron@sigma-star.at \
--cc=xenomai@lists.linux.dev \
/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).