From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/mbedtls: custom configuration file
Date: Wed, 30 Sep 2020 21:57:28 +0200 [thread overview]
Message-ID: <20200930215728.181df33f@windsurf.home> (raw)
In-Reply-To: <20200928092945.584196-1-pieter.degendt@basalte.be>
Hello Pieter,
Thanks for the proposal. See below for some questions/comments.
On Mon, 28 Sep 2020 11:29:45 +0200
Pieter De Gendt <pieter.degendt@gmail.com> wrote:
> diff --git a/package/mbedtls/mbedtls.mk b/package/mbedtls/mbedtls.mk
> index 5094434e6c..fa74197004 100644
> --- a/package/mbedtls/mbedtls.mk
> +++ b/package/mbedtls/mbedtls.mk
> @@ -68,4 +68,12 @@ else ifeq ($(BR2_microblaze)$(BR2_MIPS_CPU_MIPS32R6)$(BR2_MIPS_CPU_MIPS64R6),y)
> MBEDTLS_POST_CONFIGURE_HOOKS += MBEDTLS_DISABLE_ASM
> endif
>
> +define MBEDTLS_OVERRIDE_CONFIG
> + cp $(BR2_PACKAGE_MBEDTLS_CUSTOM_CONFIG) $(@D)/include/mbedtls/config.h
> +endef
> +
> +ifneq ($(call qstrip,$(BR2_PACKAGE_MBEDTLS_CUSTOM_CONFIG)),)
> +MBEDTLS_POST_CONFIGURE_HOOKS += MBEDTLS_OVERRIDE_CONFIG
> +endif
We prefer to enclose everything in the conditional block, and do the
qstripping once:
MBEDTLS_CUSTOM_CONFIG = $(call qstrip,$(BR2_PACKAGE_MBEDTLS_CUSTOM_CONFIG))
ifneq ($(MBEDTLS_CUSTOM_CONFIG),)
define MBEDTLS_OVERRIDE_CONFIG
..
endef
MBEDTLS_POST_CONFIGURE_HOOKS += MBEDTLS_OVERRIDE_CONFIG
endif
However, what bothers me a bit is how it completely overrides all the
configuration logic that takes place before in mbedtls.mk. For example,
if you enable BR2_PACKAGE_MBEDTLS_COMPRESSION=y and use your option to
have a custom configuration file, then what
BR2_PACKAGE_MBEDTLS_COMPRESSION=y does will be ignored.
So, we would have to make BR2_PACKAGE_MBEDTLS_COMPRESSION disappear
when BR2_PACKAGE_MBEDTLS_CUSTOM_CONFIG, but then, how do you bring zlib
as a build dependency of mbedtls ?
We need to decide if the custom configuration file should override all
tweaks, or if all tweaks should be applied on top of the custom
configuration file.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-30 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 9:29 [Buildroot] [PATCH 1/1] package/mbedtls: custom configuration file Pieter De Gendt
2020-09-30 19:57 ` Thomas Petazzoni [this message]
2020-10-01 7:29 ` Pieter De Gendt
2020-10-01 19:31 ` Yann E. MORIN
2020-10-02 7:16 ` Pieter De Gendt
2020-10-04 19:43 ` Yann E. MORIN
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=20200930215728.181df33f@windsurf.home \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox