qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2] configure: add support for pseudo-"in source tree" builds
Date: Fri, 21 Aug 2020 14:58:10 +0200	[thread overview]
Message-ID: <6414fb85-7267-2382-dc2d-f10f6c1cb115@redhat.com> (raw)
In-Reply-To: <20200821105439.GE5153@linux.fritz.box>

On 21/08/20 12:54, Kevin Wolf wrote:
>>> 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...
> I don't see what out-of-tree builds change about this unless I delete
> and reconfigure them after each step? Even in those cases where I use
> out-of-tree builds, I often reuse the same directory.

In two ways:

1) bisection will rarely jump around the point where Meson was
introduced.  First, because if it coincides with the 5.1.0 release, then
you know in advance if the problem was introduced before or after the
merge.  Second, because the bisection will quickly land on a merge
commit, and then you can (just for going down the merged branch) use a
separate out-of-tree build directory.

2) for the rare case of working on a branch that was developed pre-Meson
and has not been rebased (or need not be rebased), you again use a
separate out-of-tree build directory just for that one, and you don't
have to worry about doing distclean or an incremental builds.

Paolo



  reply	other threads:[~2020-08-21 12:59 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
2020-08-21 10:54       ` Kevin Wolf
2020-08-21 12:58         ` Paolo Bonzini [this message]
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=6414fb85-7267-2382-dc2d-f10f6c1cb115@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@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).