From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
Stefan Weil <sw@weilnetz.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH 2/2] Makefile: use full path for qapi-generated directory
Date: Thu, 01 Dec 2011 13:12:56 -0600 [thread overview]
Message-ID: <4ED7D1B8.1060604@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112011838320.31179@kaball-desktop>
On 12/01/2011 12:42 PM, Stefano Stabellini wrote:
> On Thu, 1 Dec 2011, Anthony Liguori wrote:
>> On 12/01/2011 12:11 PM, Stefan Weil wrote:
>>> Am 01.12.2011 16:19, schrieb Stefano Stabellini:
>>>> On Wed, 30 Nov 2011, Stefan Weil wrote:
>>>>> 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.
>>>>
>>>> Really? Can you provide more specific details?
>>>
>>> Yes. Suppose different generated header files with the same name
>>> exist in the source directory tree and in the build directory tree.
>>>
>>> Then compiler options (the order of -I options) will determine
>>> which of two header files with same name will be used in out-of-tree
>>> builds. If the wrong one (that from the source directory tree) is used,
>>> the compiler might fail or produce wrong code (for example when
>>> macro values changed).
>>>>> The mixed scenario creates unnecessary complexity.
>>>>> Without the mixed scenario, your patch is not needed.
>>>>
>>>> I agree that supporting the mixed scenario shouldn't be a priority.
>>>> However without this last patch a "make clean" on the main tree is not
>>>> enough to allow out of tree builds.
>>>>
>>>> Try the following scenario:
>>>>
>>>> - cd qemu; ./configure; make
>>>>
>>>> - make clean
>>>>
>>>> - cd ../temp; ./configure --source-path=../qemu; make
>>>
>>> Which ./configure do you run in an empty temp directory?
>>> This example (like similar ones in your previous mail) won't work.
>>
>> Yes, you must do external builds only from a clean source directory. This is a
>> perfectly normal requirement. In fact, I can't think of a project that doesn't
>> require this.
>
> Fair enough.
>
> In that case, like Michael Roth wrote, the patch "Makefile: use full
> path for qapi-generated directory" doesn't actually fix anything, so
> probably we don't need it either, but I'll leave it up to you.
>
Yup, it's just to address some potential issues/suggestions Stefan Weil
pointed out. I think patch 1 should be applied though.
next prev parent reply other threads:[~2011-12-01 19:13 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
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 [this message]
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=4ED7D1B8.1060604@linux.vnet.ibm.com \
--to=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 \
--cc=sw@weilnetz.de \
/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).