From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: ANNOUNCE: build system conversion to Meson has landed
Date: Fri, 21 Aug 2020 09:39:20 -0500 [thread overview]
Message-ID: <d9213548-5c05-502e-e660-fbe9b8b1f5ee@redhat.com> (raw)
In-Reply-To: <CAFEAcA-87BcmoPjY9BCodx9+m6QmhfikHv5sLVJ8w20cszDvDA@mail.gmail.com>
On 8/21/20 8:49 AM, Peter Maydell wrote:
> Hi; we've just merged Paolo's patchset that converts the build system
> to use Meson. This should mostly be fairly seamless for the average
> developer (we hope) but there are a few things to be aware of:
>
> * you probably want to do a distclean or otherwise do a clean build
> when you first update your git tree to a version of master with Meson
> (especially if you do in-tree builds)
> * out-of-tree builds should continue to work basically normally
> * we have retained compatibility for an "in-tree build" workflow where
> you run configure/make in the source tree, but this is now implemented
> by having configure create a build tree for you under-the-hood
> (but do consider switching to just doing out-of-tree builds)
If you do an in-tree build, do the 'make distclean' _before_ a 'git
pull' of the new code. If you don't clean first, the pull attempt is
likely to complain about various trace.h files, so that is a good
reminder. And if you manage to pull anyway, you may need to rewind your
tree back to v5.1.0 before attempting the in-tree 'make distclean', then
re-try the pull.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-08-21 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 13:49 ANNOUNCE: build system conversion to Meson has landed Peter Maydell
2020-08-21 14:39 ` Eric Blake [this message]
2020-08-24 12:57 ` Markus Armbruster
2020-08-21 14:50 ` Laszlo Ersek
2020-08-21 14:59 ` Paolo Bonzini
2020-08-24 10:56 ` Laszlo Ersek
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=d9213548-5c05-502e-e660-fbe9b8b1f5ee@redhat.com \
--to=eblake@redhat.com \
--cc=pbonzini@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).