From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] converting build system to Meson?
Date: Thu, 7 Mar 2019 13:22:54 +0000 [thread overview]
Message-ID: <20190307132254.GB32268@redhat.com> (raw)
In-Reply-To: <CAFEAcA_ybrfeVdGrr=fWRg8xR1Yj33xySjX14-JmPvBySqKF8w@mail.gmail.com>
On Thu, Mar 07, 2019 at 01:09:52PM +0000, Peter Maydell wrote:
> On Thu, 7 Mar 2019 at 12:56, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > In any case, this wouldn't change; as you suggest below, configure could
> > remain as a front-end (well, in-srcdir builds are not supported by
> > Meson, so "../configure && ninja" perhaps).
>
> As an aside, it might be a nice idea to drop the in-srcdir
> build altogether for QEMU anyway -- it's not really a very
> good idea and it means our build system has to cope with two
> different ways of working to no particularly useful end.
I'd be in favour of that. A huge amount of the pain I felt when
making previous changes to QEMU's makefiles has been caused by
trying to support both in-srcdir & vpath build with the same
set of rules. Fixing one often breaks the other, so you have
to cycle back & forth doing a fix in one, then testing the
other, repeat, repeat, scream, repeat.
Personally I always do in-srcdir builds, but I'd be fine to
switch to vpath builds to reduce our maint burden in the build
system as it would be a net win overall.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-03-07 13:23 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 18:12 [Qemu-devel] converting build system to Meson? Paolo Bonzini
2019-03-06 18:50 ` Marc-André Lureau
2019-03-06 21:08 ` Paolo Bonzini
2019-03-07 10:29 ` Daniel P. Berrangé
2019-03-07 6:39 ` Thomas Huth
2019-03-07 10:13 ` Peter Maydell
2019-03-07 11:11 ` Paolo Bonzini
2019-03-07 11:29 ` Dr. David Alan Gilbert
2019-03-07 11:32 ` Peter Maydell
2019-03-07 11:49 ` Marc-André Lureau
2019-03-07 11:33 ` Daniel P. Berrangé
2019-03-10 14:21 ` Markus Armbruster
2019-03-10 14:33 ` Markus Armbruster
2019-03-11 16:30 ` Paolo Bonzini
2019-03-07 10:18 ` Daniel P. Berrangé
2019-03-07 10:40 ` Paolo Bonzini
2019-03-07 10:48 ` Peter Maydell
2019-03-07 11:06 ` Paolo Bonzini
2019-03-07 10:49 ` Daniel P. Berrangé
2019-03-07 10:33 ` Stefan Hajnoczi
2019-03-07 11:54 ` Alex Bennée
2019-03-07 12:56 ` Paolo Bonzini
2019-03-07 13:09 ` Peter Maydell
2019-03-07 13:22 ` Daniel P. Berrangé [this message]
2019-03-07 18:13 ` Paolo Bonzini
2019-03-07 18:17 ` Marc-André Lureau
2019-03-07 18:18 ` Peter Maydell
2019-03-07 18:19 ` Peter Maydell
2019-03-07 19:23 ` BALATON Zoltan
2019-03-07 19:50 ` Eric Blake
2019-03-07 20:28 ` Liviu Ionescu
2019-03-08 12:19 ` Daniel P. Berrangé
2019-03-07 19:04 ` Eric Blake
2019-03-07 19:24 ` Eric Blake
2019-03-08 12:21 ` Daniel P. Berrangé
2019-03-07 18:20 ` Alex Bennée
2019-03-08 6:47 ` Gerd Hoffmann
2019-03-08 6:58 ` Thomas Huth
2019-03-08 10:31 ` Peter Maydell
2019-03-08 11:58 ` Gerd Hoffmann
2019-03-08 12:03 ` Peter Maydell
2019-03-08 16:17 ` Eric Blake
2019-03-08 16:26 ` Peter Maydell
2019-03-08 16:32 ` Paolo Bonzini
2019-03-08 16:36 ` Peter Maydell
2019-03-11 1:09 ` Neal Gompa
2019-03-07 19:05 ` Cleber Rosa
2019-03-10 16:33 ` Markus Armbruster
2019-03-10 16:28 ` Markus Armbruster
2019-03-11 6:42 ` Thomas Huth
2019-03-11 10:14 ` Daniel P. Berrangé
2019-04-18 8:21 ` Markus Armbruster
2019-04-18 8:21 ` Markus Armbruster
2019-04-18 8:35 ` Paolo Bonzini
2019-04-18 8:35 ` Paolo Bonzini
2019-05-27 16:16 ` [Qemu-devel] Status update on Meson features needed by QEMU Paolo Bonzini
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=20190307132254.GB32268@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).