qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH 2/2] Makefile: use full path for qapi-generated directory
Date: Wed, 30 Nov 2011 20:59:21 +0100	[thread overview]
Message-ID: <4ED68B19.7050704@weilnetz.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1111301227570.31179@kaball-desktop>

Am 30.11.2011 14:03, schrieb Stefano Stabellini:
> On Wed, 30 Nov 2011, Stefan Hajnoczi wrote:
>> On Tue, Nov 29, 2011 at 10:47 PM, Michael Roth
>> <mdroth@linux.vnet.ibm.com> wrote:
>>> Generally $(BUILD_DIR) == $(CURDIR), but that isn't necessarilly the
>>> case, so use $(BUILD_DIR)/qapi-generated for generated files to
>>> avoid potentionally sticking generating files in odd places outside
>>> the build's include paths.
>>> ---
>>> � Makefile | � � 2 +-
>>> � 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
>>
>> Not applied to trivial tree yet. I want to let Stefano, Stefan Weil,
>> or Anthony take a look too since we were all discussing these changes
>> yesterday.
>
> While I think that the change is correct (certainly better than the
> original patch), unfortunately still doesn't solve the problem
> entirely.
> Steps to repro, assuming "qemu" is the source tree and "temp" is the
> empty build directory:
>
> - cd qemu; ./configure; make
>
> - cd ../temp; ./configure --source-path=../qemu; make
>
> Result:
>
> Makefile:9: config-devices.mak: No such file or directory
>
> In order to fix the issue, we need to make sure that config-devices.mak
> is relative to $(BUILD_DIR) in the Makefile.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> diff --git a/Makefile b/Makefile
[snip]

It's common to use either out-of-tree builds or in-tree builds,
but not to mix both variants with a common root directory.
I think QEMU should explicitly forbid that mixed scenario (like
other projects do).

Even with your fix there can remain problems with generated
header files. The mixed scenario creates unnecessary complexity.
Without the mixed scenario, your patch is not needed.

Regards,
Stefan Weil

  reply	other threads:[~2011-11-30 20:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 17:27 [Qemu-devel] [PATCH] fix out of tree build Stefano Stabellini
2011-11-23  9:48 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2011-11-28 18:34 ` [Qemu-devel] " Stefan Weil
2011-11-28 18:45   ` Anthony Liguori
2011-11-28 20:40   ` Stefan Weil
2011-11-29 16:23     ` Stefano Stabellini
2011-11-29 22:47     ` [Qemu-devel] [PATCH 1/2] qapi: fix guardname generation Michael Roth
2011-11-29 22:47       ` [Qemu-devel] [PATCH 2/2] Makefile: use full path for qapi-generated directory Michael Roth
2011-11-30  9:10         ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2011-11-30 13:03           ` Stefano Stabellini
2011-11-30 19:59             ` Stefan Weil [this message]
2011-12-01 15:19               ` Stefano Stabellini
2011-12-01 16:05                 ` Michael Roth
2011-12-01 18:11                 ` Stefan Weil
2011-12-01 18:28                   ` Anthony Liguori
2011-12-01 18:42                     ` Stefano Stabellini
2011-12-01 19:12                       ` Michael Roth
2011-12-01 18:38                   ` Stefano Stabellini
2011-11-30  9:08       ` [Qemu-devel] [Qemu-trivial] [PATCH 1/2] qapi: fix guardname generation Stefan Hajnoczi

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=4ED68B19.7050704@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefano.stabellini@eu.citrix.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).