From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] boot/uboot: add BR2_TARGET_UBOOT_NEEDS_GNUTLS option
Date: Wed, 1 Jun 2022 23:32:22 +0200 [thread overview]
Message-ID: <20220607190458.37BAD86E22@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=a3a1da05fcc36dc256ebae98c5498ae384a65aff
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Since U-Boot 2022.04 a host dependency to gnutls is required if the
U-Boot board configuration has CONFIG_TOOLS_MKEFICAPSULE enabled. So
introduce a new BR U-Boot config option BR2_TARGET_UBOOT_NEEDS_GNUTLS
to solve this problem.
Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
boot/uboot/Config.in | 8 ++++++++
boot/uboot/uboot.mk | 4 ++++
2 files changed, 12 insertions(+)
diff --git a/boot/uboot/Config.in b/boot/uboot/Config.in
index d525faea1c..91d98c7e63 100644
--- a/boot/uboot/Config.in
+++ b/boot/uboot/Config.in
@@ -182,6 +182,14 @@ config BR2_TARGET_UBOOT_NEEDS_LZOP
the case when the board configuration has CONFIG_SPL_LZO
enabled.
+config BR2_TARGET_UBOOT_NEEDS_GNUTLS
+ bool "U-Boot needs gnutls"
+ help
+ Select this option if your U-Boot board configuration
+ requires gnutls to be available on the host. This is
+ typically the case when the board configuration has
+ CONFIG_TOOLS_MKEFICAPSULE enabled.
+
config BR2_TARGET_UBOOT_NEEDS_ATF_BL31
bool "U-Boot needs ATF BL31"
depends on BR2_TARGET_ARM_TRUSTED_FIRMWARE
diff --git a/boot/uboot/uboot.mk b/boot/uboot/uboot.mk
index cb26fc8d3e..5808e30818 100644
--- a/boot/uboot/uboot.mk
+++ b/boot/uboot/uboot.mk
@@ -227,6 +227,10 @@ ifeq ($(BR2_TARGET_UBOOT_NEEDS_LZOP),y)
UBOOT_DEPENDENCIES += host-lzop
endif
+ifeq ($(BR2_TARGET_UBOOT_NEEDS_GNUTLS),y)
+UBOOT_DEPENDENCIES += host-gnutls
+endif
+
# prior to u-boot 2013.10 the license info was in COPYING. Copy it so
# legal-info finds it
define UBOOT_COPY_OLD_LICENSE_FILE
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2022-06-07 19:25 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=20220607190458.37BAD86E22@busybox.osuosl.org \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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.