All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Liviu Ionescu" <ilg@livius.net>,
	qemu-devel@nongnu.org, "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 v3] configure: warn if not using a separate build directory
Date: Tue, 31 Mar 2020 20:28:54 +0200	[thread overview]
Message-ID: <875zeks7ix.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <32d8b69d-1641-f200-e86e-062de6c93caf@redhat.com> (Eric Blake's message of "Tue, 31 Mar 2020 12:21:32 -0500")

Eric Blake <eblake@redhat.com> writes:

> On 3/31/20 12:16 PM, 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.
>>
>> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
>> ---
>>
>
>> +if test "$in_srcdir" = "yes"; then
>> +    echo
>> +    echo "WARNING: SUPPORT FOR IN SOURCE DIR BUILDS IS DEPRECATED"
>> +    echo
>> +    echo "Support for running the 'configure' script directly from the"
>> +    echo "source directory is deprecated. In source dir builds are not"
>> +    echo "covered by automated testing and thus may not correctly build"
>> +    echo "QEMU. Users are recommended to use a separate build directory:"
>
> Our mails crossed. I still think this reads a bit awkwardly; maybe:
>
> s/IN SOURCE DIR BUILDS/BUILDING IN THE SOURCE DIR/
> s/In source dir builds/In-tree builds/
>
> Reviewed-by: Eric Blake <eblake@redhat.com>

Preferably with Eric's tweaks:
Reviewed-by: Markus Armbruster <armbru@redhat.com>



  reply	other threads:[~2020-03-31 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 17:16 [PATCH v3] configure: warn if not using a separate build directory Daniel P. Berrangé
2020-03-31 17:21 ` Eric Blake
2020-03-31 18:28   ` Markus Armbruster [this message]
2020-03-31 19:57     ` Philippe Mathieu-Daudé

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=875zeks7ix.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=berrange@redhat.com \
    --cc=eblake@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.