From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] converting build system to Meson?
Date: Thu, 7 Mar 2019 10:33:34 +0000 [thread overview]
Message-ID: <20190307103334.GD2843@stefanha-x1.localdomain> (raw)
In-Reply-To: <3246431b-8d6e-f2bc-e0f0-99d80384d97b@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
On Wed, Mar 06, 2019 at 07:12:33PM +0100, Paolo Bonzini wrote:
> lately I have been thinking of converting the QEMU build system to
> Meson. Meson is a relatively new build system that can replace
> Autotools or hand-written Makefiles such as QEMU; as a die-hard
> Autotools fan, I must say that Meson is by far better than anything else
> that has ever tried to replace Autotools, and actually has the potential
> to do so.
Meson is gaining in popularity and I recently got some experience with
it. It doesn't feel much worse or better than what QEMU or Linux have
for basic tasks. For advanced tasks, I can't say.
One frustration is that any time the meson package is upgraded (when
your distro pushes an update) it forces a rebuild from scratch :(.
I think for 95% of people Meson vs Make will make little difference (the
syntax is easy enough) and 5% of people might be able to do more
advanced things cleanly with Meson. Sounds good to me.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2019-03-07 10:33 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 [this message]
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=20190307103334.GD2843@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--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).