From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour via buildroot <buildroot@buildroot.org>
Cc: Romain Naour <romain.naour@smile.fr>,
Julien Olivain <ju.o@free.fr>, Dick Olsson <hi@senzilla.io>
Subject: Re: [Buildroot] [PATCH 1/1] boot/edk2: add a new Kconfig option to pass arbitrary build options
Date: Sun, 4 Jan 2026 11:57:39 +0100 [thread overview]
Message-ID: <20260104115739.23c1d603@windsurf> (raw)
In-Reply-To: <e3a769b8-1e3b-475a-bc43-28fd74e9864d@smile.fr>
Hello Romain,
On Sat, 5 Jul 2025 23:32:17 +0200
Romain Naour via buildroot <buildroot@buildroot.org> wrote:
> > EDK2_BUILD_OPTS += \
> > + $(call qstrip,$(BR2_TARGET_EDK2_EXTRA_BUILD_OPTS)) \
>
> Maybe we should use a loop here adding "-D" with the options provided by
> BR2_TARGET_EDK2_EXTRA_BUILD_OPTS. Otherwise the user can add whatever he want
> that could conflict with other build arguments.
No, I disagree here. If there's an option to pass extra options I
expect it to pass all my extra options, as-is with no magic. Including
if that means that I can shoot myself in the foot by passing
conflicting options.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-04 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 18:58 [Buildroot] [PATCH 1/1] boot/edk2: add a new Kconfig option to pass arbitrary build options Julien Olivain via buildroot
2025-07-05 21:32 ` Romain Naour via buildroot
2026-01-04 10:57 ` Thomas Petazzoni via buildroot [this message]
2026-01-04 10:56 ` Thomas Petazzoni via buildroot
2026-01-04 13:52 ` Julien Olivain via buildroot
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=20260104115739.23c1d603@windsurf \
--to=buildroot@buildroot.org \
--cc=hi@senzilla.io \
--cc=ju.o@free.fr \
--cc=romain.naour@smile.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox