From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v6 000/150] Meson-based build system
Date: Wed, 19 Aug 2020 21:44:35 +0200 [thread overview]
Message-ID: <72597e7a-6ee2-9875-536d-c5cd2d81950d@redhat.com> (raw)
In-Reply-To: <CAFEAcA_YU8QY_VRNdXmBV=YKuBFaX=scT0Pnk1F8JBWrrbsbJA@mail.gmail.com>
On 19/08/20 21:04, Peter Maydell wrote:
>> is it really that important? We've changed single target build
>> rules already (from subdir-x86_64-softmmu to x86_64-softmmu/all
>> for one), which broke quite some mostly automatic build
>> systems which needed some fixing. Moving executables isn't a
>> big deal after that, methinks..
> It breaks my setups and also my muscle memory for where
> executables live. So this is the limit of how much I'm
> willing to allow Meson to mess us around, I think.
It's totally possible to accomodate this and I appreciate the help and
effort you're putting into something that you (understandably) are not
too confident in.
However, this change was already in the first series that was posted
like a year ago...
Paolo
next prev parent reply other threads:[~2020-08-19 19:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 14:35 [PULL v6 000/150] Meson-based build system Paolo Bonzini
2020-08-19 18:12 ` Peter Maydell
2020-08-19 18:16 ` Peter Maydell
2020-08-19 19:05 ` Peter Maydell
2020-08-19 19:31 ` Paolo Bonzini
2020-08-19 20:07 ` Philippe Mathieu-Daudé
2020-08-19 22:27 ` Paolo Bonzini
2020-08-19 18:57 ` Michael Tokarev
2020-08-19 19:04 ` Peter Maydell
2020-08-19 19:44 ` Paolo Bonzini [this message]
2020-08-19 21:11 ` Peter Maydell
2020-08-19 23:20 ` Paolo Bonzini
2020-08-20 8:51 ` Peter Maydell
2020-08-19 20:15 ` 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=72597e7a-6ee2-9875-536d-c5cd2d81950d@redhat.com \
--to=pbonzini@redhat.com \
--cc=mjt@tls.msk.ru \
--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).