From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Liviu Ionescu" <ilg@livius.net>,
"Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Michal Suchánek" <msuchanek@suse.de>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aleksandar Markovic" <aleksandar.m.mail@gmail.com>
Subject: Re: [PATCH v4 for-5.0] configure: warn if not using a separate build directory
Date: Fri, 3 Apr 2020 09:02:46 -0500 [thread overview]
Message-ID: <93fbf486-d1c3-ec03-ea8d-163bb2374260@redhat.com> (raw)
In-Reply-To: <20200403135306.665493-1-berrange@redhat.com>
On 4/3/20 8:53 AM, Daniel P. Berrangé wrote:
> Running configure directly from the source directory is a build
> configuration that will go away in future. It is also not currently
> covered by any automated testing. Display a deprecation warning if
> the user attempts to use an in-srcdir build setup, so that they are
> aware that they're building QEMU in an undesirable manner.
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
>
> Changed in v4:
> - Adopted Eric's suggested wording
> +if test "$in_srcdir" = "yes"; then
> + echo
> + echo "WARNING: SUPPORT FOR BUILDING IN THE SOURCE DIR IS DEPRECATED"
> + echo
> + echo "Support for running the 'configure' script directly from the"
> + echo "source directory is deprecated. In-tree builds are not covered"
> + echo "by automated testing and thus may not correctly build QEMU."
> + echo "Users are recommended to use a separate build directory:"
> + echo
> + echo " $ mkdir build"
> + echo " $ cd build"
> + echo " $ ../configure"
> + echo " $ make"
Late question, but:
Since this is just a warning, we still manage to complete the
./configure run, including whatever generated files it leaves in-tree.
Is there any additional step we need to recommend prior to 'mkdir build'
that will clean up the in-tree artifacts, so that the user then
attempting the VPATH build won't still have a broken build due to the
leftovers from the in-tree attempt? 'make distclean', perhaps?
/me starts testing; I'll reply back once it finishes...
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-04-03 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 13:53 [PATCH v4 for-5.0] configure: warn if not using a separate build directory Daniel P. Berrangé
2020-04-03 14:02 ` Eric Blake [this message]
2020-04-03 14:42 ` Eric Blake
2020-04-03 22:35 ` Aleksandar Markovic
2020-04-04 9:14 ` Peter Maydell
2020-04-05 17:10 ` Aleksandar Markovic
2020-04-03 15:02 ` BALATON Zoltan
2020-04-05 14:38 ` Peter Maydell
2020-04-05 16:41 ` Aleksandar Markovic
2020-04-06 9:16 ` Daniel P. Berrangé
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=93fbf486-d1c3-ec03-ea8d-163bb2374260@redhat.com \
--to=eblake@redhat.com \
--cc=aleksandar.m.mail@gmail.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ilg@livius.net \
--cc=kwolf@redhat.com \
--cc=msuchanek@suse.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).