From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@gmail.com>
Subject: Re: [PATCH v2] configure: add support for pseudo-"in source tree" builds
Date: Fri, 21 Aug 2020 12:15:51 +0200 [thread overview]
Message-ID: <df28e5c2-ee4a-23d6-dcb2-04003a5d2757@redhat.com> (raw)
In-Reply-To: <20200821100426.GB5153@linux.fritz.box>
On 21/08/20 12:04, Kevin Wolf wrote:
>> So I'm not sure why the first build gets as far as it does, but does NOT
>> complete things and yet does not fail make, but my advice is that you should
>> NOT try to an incremental build on in-tree build when crossing the meson
>> epoch. If you are a fan of in-tree convenience, you need a ONE-TIME
>> distclean when pulling in these changes (the fact that you HAVE to clean up
>> trace.h files to merge in the meson stuff should be a hint for that). After
>> that has been done, you can go back to pretending meson supports in-tree.
> Sounds like it will be painful to switch between branches based on make
> and branches based on meson. By extension, it will also be painful to
> check out and build old versions for comparison, or doing that even more
> than once during git bisect. :-(
Not if you switch to out-of-tree builds...
Paolo
next prev parent reply other threads:[~2020-08-21 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 17:31 [PATCH v2] configure: add support for pseudo-"in source tree" builds Daniel P. Berrangé
2020-08-20 17:51 ` Philippe Mathieu-Daudé
2020-08-20 17:52 ` Eric Blake
2020-08-20 21:15 ` Eric Blake
2020-08-21 8:31 ` Daniel P. Berrangé
2020-08-21 10:04 ` Kevin Wolf
2020-08-21 10:15 ` Paolo Bonzini [this message]
2020-08-21 10:54 ` Kevin Wolf
2020-08-21 12:58 ` Paolo Bonzini
2020-08-21 10:17 ` Daniel P. Berrangé
2020-08-21 10:16 ` Paolo Bonzini
2020-08-21 10:17 ` Kevin Wolf
2020-08-21 10:31 ` Daniel P. Berrangé
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=df28e5c2-ee4a-23d6-dcb2-04003a5d2757@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).