From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] sdbus-cpp: new package
Date: Thu, 29 Aug 2019 16:24:39 +0200 [thread overview]
Message-ID: <20190829142439.GA28567@lenoch> (raw)
sdbus-c++ is a high-level C++ D-Bus library for Linux. Even though
it uses sd-bus library, it is not necessarily constrained to systemd
and can perfectly be used in non-systemd environments as well.
Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
---
Hi,
inspired by recent SQLiteC++ patch, here is sdbus-c++, so far the
best DBus library I'm aware of. I'm using it since v0.3.3, so you
should give it a try, it amazing ;-)
ladis
rules/sdbus-cpp.in | 10 ++++++++
rules/sdbus-cpp.make | 57 ++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 67 insertions(+)
create mode 100644 rules/sdbus-cpp.in
create mode 100644 rules/sdbus-cpp.make
diff --git a/rules/sdbus-cpp.in b/rules/sdbus-cpp.in
new file mode 100644
index 000000000..89675ecee
--- /dev/null
+++ b/rules/sdbus-cpp.in
@@ -0,0 +1,10 @@
+## SECTION=system_libraries
+
+config SDBUS_CPP
+ tristate
+ prompt "sdbus-cpp"
+ select HOST_CMAKE
+ select SYSTEMD
+ help
+ D-Bus IPC C++ binding library built on top of sd-bus,
+ a D-Bus C library by systemd.
diff --git a/rules/sdbus-cpp.make b/rules/sdbus-cpp.make
new file mode 100644
index 000000000..6bac2beab
--- /dev/null
+++ b/rules/sdbus-cpp.make
@@ -0,0 +1,57 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2019 by Ladislav Michl <ladis@linux-mips.org>
+#
+# For further information about the PTXdist project and license conditions
+# see the README file.
+#
+
+#
+# We provide this package
+#
+PACKAGES-$(PTXCONF_SDBUS_CPP) += sdbus-cpp
+
+#
+# Paths and names
+#
+SDBUS_CPP_VERSION := 0.7.2
+SDBUS_CPP_MD5 := b8bbaf9002ba989778967fc4f9e31e2f
+SDBUS_CPP := sdbus-cpp-$(SDBUS_CPP_VERSION)
+SDBUS_CPP_SUFFIX := tar.gz
+SDBUS_CPP_URL := https://github.com/Kistler-Group/sdbus-cpp/archive/v$(SDBUS_CPP_VERSION).$(SDBUS_CPP_SUFFIX)
+SDBUS_CPP_SOURCE := $(SRCDIR)/$(SDBUS_CPP).$(SDBUS_CPP_SUFFIX)
+SDBUS_CPP_DIR := $(BUILDDIR)/$(SDBUS_CPP)
+SDBUS_CPP_LICENSE := LGPL-2.1-only
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+SDBUS_CPP_CONF_TOOL := cmake
+SDBUS_CPP_CONF_OPT := \
+ $(CROSS_CMAKE_USR) \
+ -DBUILD_TESTS=OFF \
+ -DBUILD_CODE_GEN=OFF \
+ -DBUILD_DOC=OFF
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/sdbus-cpp.targetinstall:
+ @$(call targetinfo)
+
+ @$(call install_init, sdbus-cpp)
+ @$(call install_fixup, sdbus-cpp, PRIORITY, optional)
+ @$(call install_fixup, sdbus-cpp, SECTION, base)
+ @$(call install_fixup, sdbus-cpp, AUTHOR, "Ladislav Michl <ladis@linux-mips.org>")
+ @$(call install_fixup, sdbus-cpp, DESCRIPTION, \
+ "D-Bus IPC C++ binding library built on top of sd-bus")
+
+ @$(call install_lib, sdbus-cpp, 0, 0, 0644, libsdbus-c++)
+
+ @$(call install_finish, sdbus-cpp)
+
+ @$(call touch)
+
+# vim: syntax=make
--
2.23.0.rc1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2019-08-29 14:24 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=20190829142439.GA28567@lenoch \
--to=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.de \
/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