From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/4] Add package cryptopp
Date: Tue, 19 Apr 2016 22:23:03 +0200 [thread overview]
Message-ID: <20160419222303.56ef0520@free-electrons.com> (raw)
In-Reply-To: <1458227038-16383-2-git-send-email-julian@jusst.de>
Hello,
On Thu, 17 Mar 2016 16:03:55 +0100, Julian Scheel wrote:
> +CRYPTOPP_VERSION = 5.6.3
> +CRYPTOPP_SOURCE = cryptopp$(subst .,,$(CRYPTOPP_VERSION)).zip
> +CRYPTOPP_SITE = http://cryptopp.com/
> +CRYPTOPP_LICENSE = Boost-v1.0
> +CRYPTOPP_LICENSE_FILES = License.txt
> +CRYPTOPP_INSTALL_STAGING = YES
> +
> +HOST_CRRYPTOPP_MAKE_OPTS = \
Typo in the variable name, which means it wasn't used at all. If it had
been used, you would have spotted some build issues.
> + $(HOST_CONFIGURE_OPTS) \
> + LDFLAGS="$(HOST_LDFLAGS)"
This line is not needed, since HOST_CONFIGURE_OPTS already contains
LDFLAGS="$(HOST_LDFLAGS)". However, I had to pass
CXXFLAGS="$(HOST_CXXFLAGS) -fPIC" to make the thing build.
> +
> +define HOST_CRYPTOPP_BUILD_CMDS
> + $(MAKE) -C $(@D) $(HOST_CRYPTOPP_MAKE_OPTS) -f GNUmakefile
> + $(MAKE) -C $(@D) $(HOST_CRYPTOPP_MAKE_OPTS) libcryptopp.so
Having two lines is not needed, building the "shared" target is
sufficient.
> +endef
> +
> +define HOST_CRYPTOPP_INSTALL_CMDS
> + $(INSTALL) -d ${HOST_DIR}/usr/include/cryptopp
> + $(INSTALL) -D -m 644 $(@D)/*.h ${HOST_DIR}/usr/include/cryptopp/
> + $(INSTALL) -D -m 0755 $(@D)/libcryptopp.so ${HOST_DIR}/usr/lib/libcryptopp.so
Using the "install" target is sufficient, so I've used that instead.
> +endef
> +
> +define HOST_CRYPTOPP_EXTRACT_CMDS
> + $(UNZIP) $(DL_DIR)/$(CRYPTOPP_SOURCE) -d $(@D)
> +endef
Since extract is the first step, we usually put this before the
build/install commands.
I've fixed up those issues and applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-19 20:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 15:03 [Buildroot] [PATCHv2 0/4] Add flashing tools for tegra processors Julian Scheel
2016-03-17 15:03 ` [Buildroot] [PATCHv2 1/4] Add package cryptopp Julian Scheel
2016-04-19 20:23 ` Thomas Petazzoni [this message]
2016-04-21 20:40 ` Thomas Petazzoni
2016-04-22 7:29 ` Julian Scheel
2016-03-17 15:03 ` [Buildroot] [PATCHv2 2/4] Add package tegrarcm Julian Scheel
2016-04-19 20:24 ` Thomas Petazzoni
2016-03-17 15:03 ` [Buildroot] [PATCHv2 3/4] Add package cbootimage Julian Scheel
2016-04-19 20:34 ` Thomas Petazzoni
2016-03-17 15:03 ` [Buildroot] [PATCHv2 4/4] Add package cbootimage-configs Julian Scheel
2016-04-19 21:08 ` Thomas Petazzoni
2016-04-19 22:36 ` Arnout Vandecappelle
2016-04-20 6:18 ` Julian Scheel
2016-04-20 7:11 ` Thomas Petazzoni
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=20160419222303.56ef0520@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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