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: Thu, 01 Dec 2011 19:11:14 +0100 [thread overview]
Message-ID: <4ED7C342.3060302@weilnetz.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1112011048150.31179@kaball-desktop>
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.
>
> this has to work, right? It does not without the patch to fix the
> generation of config-devices.mak.
No. You'll need a 'make distclean'. If that does what it should do,
a following out-of-tree build will work.
Regards,
Stefan Weil
next prev parent reply other threads:[~2011-12-01 18:12 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 [this message]
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=4ED7C342.3060302@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).