From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, pbonzini@redhat.com
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2 5/5] configure: allow the selection of alternate config in the build
Date: Wed, 7 Jul 2021 08:16:26 -0700 [thread overview]
Message-ID: <85d9f5fb-36a7-4c25-411e-f3cd9cbcecd7@linaro.org> (raw)
In-Reply-To: <20210707131744.26027-6-alex.bennee@linaro.org>
On 7/7/21 6:17 AM, Alex Bennée wrote:
> While the default config works well enough it does end up enabling a
> lot of stuff. For more minimal builds we can select a different list
> of devices and let Kconfig work out what we want. For example:
>
> ../../configure --without-default-features \
> --target-list=arm-softmmu,aarch64-softmmu \
> --with-devices-aarch64=minimal
>
> will override the aarch64-softmmu default set of devices with a more
> minimal set of devices that just enables the virt and sbsa-ref models.
>
> Signed-off-by: Alex Bennée<alex.bennee@linaro.org>
> Cc: Philippe Mathieu-Daudé<philmd@redhat.com>
> Cc: Paolo Bonzini<pbonzini@redhat.com>
> Message-Id:<20210621152120.4465-6-alex.bennee@linaro.org>
I guess I can just follow the shell scripting. It's a shame we can't just put together
the properties section contents while we're parsing the command-line, and instead have to
break it up into N variables.
> + # unroll any custom device configs
> + if test -n "$device_archs"; then
> + for a in $device_archs; do
> + eval "c=\$devices_${a}"
> + echo "${a}-softmmu = '$c'" >> $cross
> + done
> + fi
Do you really need the IF around the FOR? Shouldn't the loop iterate zero times if
$device_archs is empty?
Otherwise,
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2021-07-07 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 13:17 [PATCH for 6.1 v2 0/5] custom device configs Alex Bennée
2021-07-07 13:17 ` [PATCH v2 1/5] meson: Introduce target-specific Kconfig Alex Bennée
2021-07-07 13:17 ` [PATCH v2 2/5] hw/arm: add dependency on OR_IRQ for XLNX_VERSAL Alex Bennée
2021-07-07 13:17 ` [PATCH v2 3/5] hw/arm: move CONFIG_V7M out of default-devices Alex Bennée
2021-07-07 13:17 ` [PATCH v2 4/5] configs: rename default-configs to configs and reorganise Alex Bennée
2021-07-07 15:09 ` Richard Henderson
2021-07-07 13:17 ` [PATCH v2 5/5] configure: allow the selection of alternate config in the build Alex Bennée
2021-07-07 15:16 ` Richard Henderson [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=85d9f5fb-36a7-4c25-411e-f3cd9cbcecd7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).