From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] git-crypt: new package
Date: Mon, 30 Jan 2017 15:36:54 +0100 [thread overview]
Message-ID: <87efzk8vi1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170130135517.5010-1-francesconegri@gmail.com> (Francesco Negri's message of "Mon, 30 Jan 2017 14:55:17 +0100")
>>>>> "Francesco" == Francesco Negri <francesconegri@gmail.com> writes:
> Signed-off-by: Francesco Negri <francesconegri@gmail.com>
> ---
> Changes v3 -> v4:
> - more accurate info on licenses
> ---
> package/Config.in | 1 +
> package/git-crypt/Config.in | 15 +++++++++++++++
> package/git-crypt/git-crypt.hash | 2 ++
> package/git-crypt/git-crypt.mk | 21 +++++++++++++++++++++
> 4 files changed, 39 insertions(+)
> create mode 100644 package/git-crypt/Config.in
> create mode 100644 package/git-crypt/git-crypt.hash
> create mode 100644 package/git-crypt/git-crypt.mk
> diff --git a/package/Config.in b/package/Config.in
> index 6a3a1a7c7..067ff3cc9 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -138,6 +138,7 @@ menu "Development tools"
> source "package/gawk/Config.in"
> source "package/gettext/Config.in"
> source "package/git/Config.in"
> + source "package/git-crypt/Config.in"
> source "package/gperf/Config.in"
> source "package/grep/Config.in"
> source "package/jq/Config.in"
> diff --git a/package/git-crypt/Config.in b/package/git-crypt/Config.in
> new file mode 100644
> index 000000000..4e1ca4a2b
> --- /dev/null
> +++ b/package/git-crypt/Config.in
> @@ -0,0 +1,15 @@
> +config BR2_PACKAGE_GIT_CRYPT
> + bool "git-crypt"
> + depends on BR2_INSTALL_LIBSTDCPP
> + depends on BR2_USE_MMU # git
> + select BR2_PACKAGE_GIT
git is only used at runtime, not build time - So we normally add a
comment about that (and drop it from GIT_CRYPT_DEPENDENCIES).
> new file mode 100644
> index 000000000..fc3e44f81
> --- /dev/null
> +++ b/package/git-crypt/git-crypt.mk
> @@ -0,0 +1,21 @@
> +################################################################################
> +#
> +# git-crypt
> +#
> +################################################################################
> +
> +GIT_CRYPT_VERSION = 0.5.0
> +GIT_CRYPT_SITE = https://www.agwa.name/projects/git-crypt/downloads
> +GIT_CRYPT_DEPENDENCIES = git openssl
> +GIT_CRYPT_LICENSE = GPLv3+, MIT
> +GIT_CRYPT_LICENSE_FILES = COPYING parse_options.hpp
> +
> +define GIT_CRYPT_BUILD_CMDS
> + $(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D) all
The reason you had to add TARGET_CONFIGURE_OPTS before make was that the
build system hardcoded -lcrypto to link with openssl. This is
unfortunately not enough when linking statically as you also have to
consider the dependencies of openssl (E.G. zlib).
So I changed it to host pkg-config to get the libraries needed for
openssl and pass those in LDFLAGS.
> +endef
> +
> +define GIT_CRYPT_INSTALL_TARGET_CMDS
> + $(INSTALL) -D -m 0755 $(@D)/git-crypt $(TARGET_DIR)/usr/bin/git-crypt
The buildsystem has a sensible 'make install' target, so I rewrote it to
use that.
Committed with these fixes, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-01-30 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 0:28 [Buildroot] [PATCH 1/1] git-crypt: new package Francesco Negri
2017-01-30 5:28 ` Baruch Siach
2017-01-30 9:38 ` Francesco Negri
2017-01-30 10:54 ` Thomas Petazzoni
2017-01-30 10:58 ` [Buildroot] [PATCH v2 " Francesco Negri
2017-01-30 11:02 ` Baruch Siach
2017-01-30 11:07 ` Francesco Negri
2017-01-30 12:08 ` Francesco Negri
2017-01-30 12:28 ` Baruch Siach
2017-01-30 13:27 ` [Buildroot] [PATCH v3 " Francesco Negri
2017-01-30 13:38 ` Baruch Siach
2017-01-30 13:55 ` [Buildroot] [PATCH v4 " Francesco Negri
2017-01-30 14:36 ` Peter Korsgaard [this message]
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=87efzk8vi1.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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