From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [RFC PATCH] meson: Only install ROMs when building system emulation binaries
Date: Fri, 15 Jan 2021 19:53:15 +0100 [thread overview]
Message-ID: <7acbc6ab-c97d-ada4-8ce2-481b6000b5b6@redhat.com> (raw)
In-Reply-To: <20210115175135.3402714-1-philmd@redhat.com>
On 15/01/21 18:51, Philippe Mathieu-Daudé wrote:
> It is pointless to install ROM blobs for user emulation.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> RFC because I think it would be better to make the 'blobs'
> option a 'feature' instead of a boolean so we can set it
> as 'auto' and then in that case we could do something
Yes it's better to do that and have
install_blobs = get_option('install_blobs').enabled() or
(get_option('install_blobs').auto() and have_system)
And then if get_option('install_blobs').auto() you could install blobs
only if the corresponding target is included in target_dirs:
if get_option('install_blobs').enabled() or 'i386-softmmu' in
target_dirs or 'x86_64-softmmu' in target_dirs
...
endif
Paolo
> blobs = have_system
>
> because currently ./configure still displays:
>
> Install blobs: YES
>
> which is confusing.
> ---
> meson.build | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index 954152c90fe..273b8e6baa9 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -2254,7 +2254,9 @@
>
> subdir('scripts')
> subdir('tools')
> -subdir('pc-bios')
> +if have_system
> + subdir('pc-bios')
> +endif
> subdir('docs')
> subdir('tests')
> if gtk.found()
>
prev parent reply other threads:[~2021-01-15 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 17:51 [RFC PATCH] meson: Only install ROMs when building system emulation binaries Philippe Mathieu-Daudé
2021-01-15 18:53 ` Paolo Bonzini [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=7acbc6ab-c97d-ada4-8ce2-481b6000b5b6@redhat.com \
--to=pbonzini@redhat.com \
--cc=laurent@vivier.eu \
--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 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.