From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: Re: [ptxdist] [APPLIED] libubootenv: Make yaml support optional
Date: Mon, 22 Sep 2025 13:04:28 +0200 [thread overview]
Message-ID: <20250922110428.2077112-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250919100643.199174-6-ada@thorsis.com>
Thanks, applied as 1a4e37486db0139a3fcffbd6676b26fce2d51afd.
Michael
[sent from post-receive hook]
On Mon, 22 Sep 2025 13:04:28 +0200, Alexander Dahl <ada@thorsis.com> wrote:
> If just used as drop in replacement with the old configuration format,
> libyaml dependency is not required. You only need to enable it, if you
> intend to use the new, extended configuration format.
>
> Link: https://github.com/sbabic/libubootenv/blob/master/docs/fw_env_config.md#configuration-file-in-yaml
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> Message-Id: <20250919100643.199174-6-ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libubootenv.in b/rules/libubootenv.in
> index 317a440fc0de..3bee47481cb0 100644
> --- a/rules/libubootenv.in
> +++ b/rules/libubootenv.in
> @@ -3,7 +3,7 @@
> menuconfig LIBUBOOTENV
> tristate
> select HOST_CMAKE
> - select LIBYAML
> + select LIBYAML if LIBUBOOTENV_YAML_CONFIG
> select ZLIB
> prompt "libubootenv "
> help
> @@ -21,6 +21,12 @@ config LIBUBOOTENV_TOOLS
> help
> Install fw_printenv and fw_setenv to target.
>
> +config LIBUBOOTENV_YAML_CONFIG
> + bool
> + prompt "extended conf file format"
> + help
> + Support the new, extended, yaml based configuration file format.
> +
> comment "u-boot-tools is selected!"
> depends on U_BOOT_TOOLS
>
> diff --git a/rules/libubootenv.make b/rules/libubootenv.make
> index d6753cd87081..1ec86693a4e3 100644
> --- a/rules/libubootenv.make
> +++ b/rules/libubootenv.make
> @@ -35,7 +35,7 @@ LIBUBOOTENV_CONF_TOOL := cmake
> LIBUBOOTENV_CONF_OPT := \
> $(CROSS_CMAKE_USR) \
> -DBUILD_DOC=OFF \
> - -DNO_YML_SUPPORT=OFF
> + -DNO_YML_SUPPORT=$(call ptx/ifdef, PTXCONF_LIBUBOOTENV_YAML_CONFIG, OFF, ON)
>
> # ----------------------------------------------------------------------------
> # Target-Install
prev parent reply other threads:[~2025-09-22 11:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 10:06 [ptxdist] [PATCH v2 0/5] libubootenv: New package to replace target u-boot-tools Alexander Dahl via ptxdist
2025-09-19 10:06 ` [ptxdist] [PATCH v2 1/5] libubootenv: Introduce new package Alexander Dahl via ptxdist
2025-09-22 11:04 ` [ptxdist] [APPLIED] " Michael Olbrich
2025-09-19 10:06 ` [ptxdist] [PATCH v2 2/5] libubootenv: Add option for installing tools Alexander Dahl via ptxdist
2025-09-22 11:04 ` [ptxdist] [APPLIED] " Michael Olbrich
2025-09-19 10:06 ` [ptxdist] [PATCH v2 3/5] libubootenv: Install config file to target Alexander Dahl via ptxdist
2025-09-22 11:04 ` [ptxdist] [APPLIED] " Michael Olbrich
2025-09-19 10:06 ` [ptxdist] [PATCH v2 4/5] libubootenv: Import some fixes from master Alexander Dahl via ptxdist
2025-09-22 11:04 ` [ptxdist] [APPLIED] " Michael Olbrich
2025-09-19 10:06 ` [ptxdist] [PATCH v2 5/5] libubootenv: Make yaml support optional Alexander Dahl via ptxdist
2025-09-22 11:04 ` Michael Olbrich [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=20250922110428.2077112-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
/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