From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] package/libsodium: add config for full build
Date: Sat, 28 Sep 2019 23:19:34 +0200 [thread overview]
Message-ID: <20190928231934.236e5f83@windsurf> (raw)
In-Reply-To: <20190923082902.28472-1-adrien@gallouet.fr>
Hello,
On Mon, 23 Sep 2019 08:29:03 +0000
Adrien Gallou?t <adrien@gallouet.fr> wrote:
> +config BR2_PACKAGE_LIBSODIUM_FULL
> + bool "all functions"
> + default y
> + help
> + Build all seldom used and obsolete functions. Without
> + this option, only the minimal set of normally used
> + functions is built.
> +
> +endif
> diff --git a/package/libsodium/libsodium.mk b/package/libsodium/libsodium.mk
> index a94a8271c5..9afa09ff37 100644
> --- a/package/libsodium/libsodium.mk
> +++ b/package/libsodium/libsodium.mk
> @@ -14,5 +14,9 @@ ifeq ($(BR2_TOOLCHAIN_SUPPORTS_PIE),)
> LIBSODIUM_CONF_OPTS += --disable-pie
> endif
>
> +ifeq ($(BR2_PACKAGE_LIBSODIUM_FULL),)
> +LIBSODIUM_CONF_OPTS += --enable-minimal
But then, does it make sense to invert the option and name it
BR2_PACKAGE_LIBSODIUM_MINIMAL ? It would match the
--enable-minimal/--disable-minimal autoconf options of libsodium.
Also, we need to pass --disable-minimal in an "else" clause.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-28 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 8:29 [Buildroot] [PATCH v4 1/1] package/libsodium: add config for full build Adrien Gallouët
2019-09-28 21:19 ` Thomas Petazzoni [this message]
2019-09-28 21:49 ` Adrien Gallouët
2019-09-29 7:04 ` Thomas Petazzoni
2019-09-29 10:51 ` Arnout Vandecappelle
2019-09-30 12:04 ` Peter Korsgaard
2019-09-30 12:29 ` Thomas Petazzoni
2019-10-24 8:30 ` Peter Korsgaard
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=20190928231934.236e5f83@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.