From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, Thomas Huth <thuth@redhat.com>
Cc: "Richard Henderson" <rth@twiddle.net>,
qemu-devel <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] converting build system to Meson?
Date: Thu, 7 Mar 2019 12:11:04 +0100 [thread overview]
Message-ID: <baa5b3a8-6b74-cbf1-8ae7-a9c91cb9e90c@redhat.com> (raw)
In-Reply-To: <CAFEAcA_RQU+HYczN4Z=vEL8U31---GTi_HOxg8y50pzX8p+p7Q@mail.gmail.com>
On 07/03/19 11:13, Peter Maydell wrote:
> Yes, that tends to be my view. Our current build system:
> * has no dependencies that are problematic for older hosts
> (contrast Meson, which needs Python 3.5, even if we take
> the drastic step of shipping an entire build tool along
> with QEMU; OSX python is 2.7 still)
Regarding OS X, don't we require Homebrew anyway? (We will have to deal
with the Python 2 issue sometime in 2020, and I don't expect much
happening wrt Meson in QEMU before then).
> * is not particularly hard to deal with for the common cases
> ("add new source file" is straightforward)
> * covers all our requirements as far as I'm aware
> (whereas you've listed a couple of places where Meson
> would need changes/extensions to support things we do already)
Indeed---I mentioned that rejection of these changes/extensions would be
a blocker. I think those extensions are useful anyway, so I am
contributing them to Meson even if we don't end up using them. My
experience so far with the Meson community makes me positive that _some_
kind of solution will be found even if it's not what I'm proposing.
> (This might change in the future, eg if Meson catches on to the
> extent that everybody is using it and competitors like CMake are
> more obviously eclipsed by it, in the way that git took over
> from svn and relegated mercurial and bzr to obscurity.)
It's very hard to displace established contenders in this area because
unlike, switching to git or svn, a switch involves a major rewrite
effort. Nevertheless, big projects _are_ switching.
Meson has a very different design than Autotools or even CMake, despite
the apparent similarity with the latter. The lack of an escape
mechanism sounds annoying, but it is much less of a problem than you'd
think. In fact it has the interesting side effect, of discouraging
forks very much: new features are contributed upstream for everyone's
use and vetted by the Meson developers.
This makes Meson way more polished than CMake or Autotools, or
hand-crafted Makefile such as ours; so it takes more effort to switch,
but the result is good. I have started following Meson about a year
ago, and a lot of missing features have been added since then, slowly
but surely, which is why I am only reaching out now to you and others.
Paolo
next prev parent reply other threads:[~2019-03-07 11:11 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 [this message]
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é
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=baa5b3a8-6b74-cbf1-8ae7-a9c91cb9e90c@redhat.com \
--to=pbonzini@redhat.com \
--cc=marcandre.lureau@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).