From: Paolo Bonzini <pbonzini@redhat.com>
To: "Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Markus Armbruster <armbru@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: deprecation of in-tree builds
Date: Tue, 31 Mar 2020 09:48:52 +0200 [thread overview]
Message-ID: <c0a1dc94-c3f2-696e-743f-aa15ef995094@redhat.com> (raw)
In-Reply-To: <20200330143759.GD6139@linux.fritz.box>
On 30/03/20 16:37, Kevin Wolf wrote:
> If manually dealing with separate build directories is inconvenient
> today, it will still be inconvenient with Meson, so this would mean
> introducing the automatic directly creation together with the other
> changes to enable Meson. Which is fine by me, as long as it is really
> done when the external directory becomes mandatory, so that people won't
> have to switch back and forth between directories.
Serious question: why is automatic directly creation more convenient for
developers? Even if "./configure" generates a "build" directory for
you, you would still have to invoke the QEMU binary as
"build/x86_64-softmmu/qemu-system-x86_64". That is less convenient than
doing "mkdir build" in the first place.
I can see why it's more convenient for packaging, as they just invoke
"make" and "make install", but as far as developers are concerned it
seems to add complexity for little or no gain.
Thanks,
Paolo
next prev parent reply other threads:[~2020-03-31 7:50 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 20:50 deprecation of in-tree builds Peter Maydell
2020-03-21 22:50 ` BALATON Zoltan
2020-03-23 13:32 ` Stefan Hajnoczi
2020-03-24 13:54 ` Eric Blake
2020-08-18 19:14 ` Peter Maydell
2020-08-20 10:54 ` Kevin Wolf
2020-08-20 11:14 ` Michael Tokarev
2020-08-20 11:56 ` Paolo Bonzini
2020-08-20 12:00 ` Peter Maydell
2020-08-20 13:30 ` Kevin Wolf
2020-08-20 14:10 ` Peter Maydell
2020-08-20 15:50 ` Paolo Bonzini
2020-08-20 16:14 ` Kevin Wolf
2020-08-20 17:39 ` Paolo Bonzini
2020-08-21 9:55 ` Gerd Hoffmann
2020-08-20 16:05 ` Daniel P. Berrangé
[not found] ` <CAL1e-=gKB0qRxGntXrU0im2gjMh1tq_SLGTm+HsmgBRGXQ9+Bg@mail.gmail.com>
2020-03-22 17:20 ` Peter Maydell
2020-03-22 19:51 ` Aleksandar Markovic
2020-03-22 20:14 ` Peter Maydell
2020-03-22 20:45 ` Aleksandar Markovic
2020-03-22 20:46 ` BALATON Zoltan
2020-03-22 21:15 ` Peter Maydell
2020-03-23 0:35 ` BALATON Zoltan
2020-03-23 10:20 ` Daniel P. Berrangé
2020-03-30 13:26 ` Markus Armbruster
2020-03-30 13:31 ` Peter Maydell
2020-03-30 13:42 ` Daniel P. Berrangé
2020-03-30 14:37 ` Kevin Wolf
2020-03-30 17:29 ` Michal Suchánek
2020-03-30 17:36 ` Daniel P. Berrangé
2020-03-30 20:15 ` BALATON Zoltan
2020-03-31 7:48 ` Paolo Bonzini [this message]
2020-03-31 9:20 ` Liviu Ionescu
2020-03-31 10:19 ` Peter Maydell
2020-03-31 11:46 ` Liviu Ionescu
2020-03-31 12:07 ` Kevin Wolf
2020-03-31 15:23 ` Liviu Ionescu
2020-03-31 12:02 ` Kevin Wolf
2020-03-31 12:05 ` Peter Maydell
2020-03-31 12:24 ` Kevin Wolf
2020-03-31 12:32 ` Peter Maydell
2020-03-31 15:08 ` Eric Blake
2020-03-31 15:20 ` BALATON Zoltan
2020-03-31 15:44 ` Kevin Wolf
2020-03-31 12:54 ` BALATON Zoltan
2020-03-30 16:25 ` Aleksandar Markovic
2020-03-31 7:15 ` Markus Armbruster
2020-03-31 12:33 ` BALATON Zoltan
2020-03-31 12:50 ` Daniel P. Berrangé
2020-03-31 15:04 ` BALATON Zoltan
2020-03-31 15:23 ` Daniel P. Berrangé
2020-03-31 15:55 ` BALATON Zoltan
2020-03-31 10:38 ` 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=c0a1dc94-c3f2-696e-743f-aa15ef995094@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--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).