The p11-kit-remote executable is now located under $libexecdir, but we
should use the p11-kit command to launch the subcommand.
CHECK_PROGS =
+CLEANFILES =
+
EXTRA_DIST = HACKING
incdir = $(includedir)/p11-kit-1/p11-kit
po/Makefile.in
p11-kit/p11-kit-1.pc
p11-kit/pkcs11.conf.example
- p11-kit/p11-kit-remote@.service
trust/trust-extract-compat
trust/test-extract
])
exampledir = $(p11_system_config)
example_DATA = p11-kit/pkcs11.conf.example
+p11-kit/p11-kit-remote@.service: p11-kit/p11-kit-remote@.service.in
+ $(AM_V_GEN) sed -e 's|@bindir[@]|$(bindir)|g' \
+ -e 's|@libdir[@]|$(libdir)|g' $< > $@.tmp && \
+ mv $@.tmp $@
+
+CLEANFILES += p11-kit/p11-kit-remote@.service
+
EXTRA_DIST += \
p11-kit/docs.h \
p11-kit/p11-kit-remote.socket \
+ p11-kit/p11-kit-remote@.service.in \
$(NULL)
bin_PROGRAMS += p11-kit/p11-kit
StandardInput=socket
StandardOutput=socket
StandardError=journal
-ExecStart=@libdir@/p11-kit/p11-kit-remote @libdir@/p11-kit-proxy.so
+ExecStart=@bindir@/p11-kit remote @libdir@/p11-kit-proxy.so