From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: pc-bios/optionrom: when/why do we build it?
Date: Fri, 22 Nov 2024 09:20:49 +0100 [thread overview]
Message-ID: <0facde38-6026-4c08-bcb5-4ba2ec562cf9@redhat.com> (raw)
In-Reply-To: <ec822e92-179a-44e3-80d4-48763544689f@tls.msk.ru>
On 11/22/24 08:05, Michael Tokarev wrote:
> Maybe a more general question would be:
> what is our main build entry point? Is it `make` (or `make all`)
> still, or is it meson now?
s/meson/ninja/
But no, it's always make. Using make ensures that:
1) you build stuff that is not emulators (option ROMs, TCG tests).
Meson is only for stuff that runs on the host
2) you rerun configure if it changes.
> For this specific optionrom thing, I'd say we should add a separate
> rule to the top-level Makefile (or to meson.build) which is not
> run by default but can be run explicitly, like `make optionrom` -
> this will check if pc-bios/optionrom/config.mak is there and either
> run make in this subdir or complain saying no i386 compiler is found.
The optionroms are built by default to ensure that they do not bitrot.
I think they're not copied (this is really old policy...) so that, if
there is no need, the binary does not change at all across releases.
But yes, adding an explicit makefile target is useful. It could also
copy the build products over to the source directory.
Paolo
prev parent reply other threads:[~2024-11-22 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 6:58 pc-bios/optionrom: when/why do we build it? Michael Tokarev
2024-11-22 7:05 ` Michael Tokarev
2024-11-22 8:20 ` 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=0facde38-6026-4c08-bcb5-4ba2ec562cf9@redhat.com \
--to=pbonzini@redhat.com \
--cc=mjt@tls.msk.ru \
--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).