From: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Liviu Ionescu" <ilg@livius.net>,
"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: Sun, 5 Apr 2020 18:41:35 +0200 [thread overview]
Message-ID: <CAHiYmc7V1AS2=Pz2nT80S2BhZ8fCB6vWRfPAB4zDvdnO0J-T=Q@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_CSiw4ojYHVD6S73O-iRuXt6gTS=3VdAO545q8ye0+Ww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
16:39 Ned, 05.04.2020. Peter Maydell <peter.maydell@linaro.org> је
написао/ла:
>
> On Fri, 3 Apr 2020 at 14:53, Daniel P. Berrangé <berrange@redhat.com>
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>
> > ---
>
> > +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"
> > + echo
> > +fi
>
> So here's my stab at some text here; I'm aiming at nudging users
> towards out-of-tree builds if they were simply not thinking about
> it, but not actively marking them as 'deprecated', since it sounded
> to me like we were planning to keep at least the basic
> 'configure+make+make install' sequence of commands working.
>
> echo "NOTE: we recommend against building in the source directory"
> echo
> echo "You've run the 'configure' script directly from the source"
> echo "directory. This will work, but we recommend using a separate"
> echo "build directory, especially if you plan to work with the QEMU"
> echo "sources rather than just building it once. You can switch to"
> echo "a separate build directory like this:"
> [instructions go here]
>
Peter's version is far more superior to Daniel's.
I'd better not discuss the reasons, not wanting to waste my time and
other's time.
For Peter's version:
Reviewed-by: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
> thanks
> -- PMM
>
[-- Attachment #2: Type: text/html, Size: 3693 bytes --]
next prev parent reply other threads:[~2020-04-05 16:42 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
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 [this message]
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='CAHiYmc7V1AS2=Pz2nT80S2BhZ8fCB6vWRfPAB4zDvdnO0J-T=Q@mail.gmail.com' \
--to=aleksandar.qemu.devel@gmail.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).