On Wed, 15 Apr 2020 at 07:13, Markus Armbruster wrote:
> Peter Maydell writes:
> > Given where we are in the release cycle, I think this isn't
> > going to go in for 5.0; and it's not really that urgent now
> > we've decided we don't want to actually deprecate in-tree builds.
>
> Have we?
>
> We
Peter Maydell writes:
> On Mon, 6 Apr 2020 at 16:33, 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
On Mon, 6 Apr 2020 at 16:33, 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-src
On Mon, Apr 06, 2020 at 10:38:45AM -0500, Eric Blake wrote:
> On 4/6/20 10:33 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 dep
On 4/6/20 10:33 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
Calling it a deprecation warning may be overkill n
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
