From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Subject: Re: [PATCH] build: further refine build.ninja rules
Date: Fri, 9 Jun 2023 13:14:44 +0200 [thread overview]
Message-ID: <12f7b5ec-708a-0dcf-f80e-58581cf66761@linaro.org> (raw)
In-Reply-To: <20230608134314.943615-1-pbonzini@redhat.com>
On 8/6/23 15:43, Paolo Bonzini wrote:
> In commit b0fcc6fc7fc1 ("build: rebuild build.ninja using
> "meson setup --reconfigure"", 2023-05-19) I changed the build.ninja
> rule in the Makefile to use "meson setup" so that the Makefile would
> pick up a changed path to the meson binary.
>
> However, there was a reason why build.ninja was rebuilt using $(NINJA)
> itself. Namely, ninja has its own cache of file modification times,
> and if it does not know about the modification that was done outside
> its control, it will *also* try to regenerate build.ninja. This can be
> simply by running "make" on a fresh tree immediately after "configure";
> that will trigger an unnecessary meson run.
>
> So, apply a refinement to the rule in order to cover both cases:
>
> - track the meson binary that was used (and that is embedded in
> build.ninja's reconfigure rules); to do this, write build.ninja.stamp
> right after executing meson successfully
>
> - if it changed, force usage of "$(MESON) setup --reconfigure" to
> update the path in the reconfigure rule
>
> - if it didn't change, use "$(NINJA) build.ninja" just like before
> commit b0fcc6fc7fc1.
>
> Reported-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> Makefile | 17 +++++++++++++----
> configure | 1 +
> 2 files changed, 14 insertions(+), 4 deletions(-)
Tested-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2023-06-09 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 13:43 [PATCH] build: further refine build.ninja rules Paolo Bonzini
2023-06-08 19:21 ` Mark Cave-Ayland
2023-06-09 11:14 ` Philippe Mathieu-Daudé [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=12f7b5ec-708a-0dcf-f80e-58581cf66761@linaro.org \
--to=philmd@linaro.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@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).