From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Cc: Clemens Gruber <clemens.gruber@pqgruber.com>
Subject: [ptxdist] [PATCH] libsodium: new package
Date: Sun, 28 Aug 2016 15:10:46 +0200 [thread overview]
Message-ID: <20160828131046.23120-1-clemens.gruber@pqgruber.com> (raw)
Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>
---
rules/libsodium.in | 12 +++++++++++
rules/libsodium.make | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 71 insertions(+)
create mode 100644 rules/libsodium.in
create mode 100644 rules/libsodium.make
diff --git a/rules/libsodium.in b/rules/libsodium.in
new file mode 100644
index 0000000..e621a1b
--- /dev/null
+++ b/rules/libsodium.in
@@ -0,0 +1,12 @@
+## SECTION=system_libraries
+
+config LIBSODIUM
+ bool
+ prompt "libsodium"
+ help
+ Sodium is a new, easy-to-use software library for encryption,
+ decryption, signatures, password hashing and more.
+ It is a portable, cross-compilable, installable, packageable fork of
+ NaCl, with a compatible API, and an extended API to improve usability
+ even further. Its goal is to provide all of the core operations
+ needed to build higher-level cryptographic tools.
diff --git a/rules/libsodium.make b/rules/libsodium.make
new file mode 100644
index 0000000..d8036d7
--- /dev/null
+++ b/rules/libsodium.make
@@ -0,0 +1,59 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2016 by Clemens Gruber <clemens.gruber@pqgruber.com>
+#
+# See CREDITS for details about who has contributed to this project.
+#
+# For further information about the PTXdist project and license conditions
+# see the README file.
+#
+
+#
+# We provide this package
+#
+PACKAGES-$(PTXCONF_LIBSODIUM) += libsodium
+
+#
+# Paths and names
+#
+LIBSODIUM_VERSION := 1.0.11
+LIBSODIUM_MD5 := b58928d035064b2a46fb564937b83540
+LIBSODIUM := libsodium-$(LIBSODIUM_VERSION)
+LIBSODIUM_SUFFIX := tar.gz
+LIBSODIUM_URL := https://github.com/jedisct1/libsodium/releases/download/$(LIBSODIUM_VERSION)/$(LIBSODIUM).$(LIBSODIUM_SUFFIX)
+LIBSODIUM_SOURCE := $(SRCDIR)/$(LIBSODIUM).$(LIBSODIUM_SUFFIX)
+LIBSODIUM_DIR := $(BUILDDIR)/$(LIBSODIUM)
+LIBSODIUM_LICENSE := ISC
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+#
+# autoconf
+#
+LIBSODIUM_CONF_TOOL := autoconf
+LIBSODIUM_CONF_OPT := \
+ $(CROSS_AUTOCONF_USR) \
+ --disable-static
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/libsodium.targetinstall:
+ @$(call targetinfo)
+
+ @$(call install_init, libsodium)
+ @$(call install_fixup, libsodium, PRIORITY, optional)
+ @$(call install_fixup, libsodium, SECTION, base)
+ @$(call install_fixup, libsodium, AUTHOR, "Clemens Gruber <clemens.gruber@pqgruber.com>")
+ @$(call install_fixup, libsodium, DESCRIPTION, missing)
+
+ @$(call install_lib, libsodium, 0, 0, 0644, libsodium)
+
+ @$(call install_finish, libsodium)
+
+ @$(call touch)
+
+# vim: syntax=make
--
2.9.3
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2016-08-28 13:11 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=20160828131046.23120-1-clemens.gruber@pqgruber.com \
--to=clemens.gruber@pqgruber.com \
--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