From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:53410)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1TjVs7-00074W-HH
	for qemu-devel@nongnu.org; Fri, 14 Dec 2012 09:04:16 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1TjVs4-0004vk-Gj
	for qemu-devel@nongnu.org; Fri, 14 Dec 2012 09:04:15 -0500
Received: from mx1.redhat.com ([209.132.183.28]:48518)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1TjVs4-0004vc-AD
	for qemu-devel@nongnu.org; Fri, 14 Dec 2012 09:04:12 -0500
Message-ID: <50CB2E9C.4010600@redhat.com>
Date: Fri, 14 Dec 2012 14:50:20 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1936665411.23874741.1355472843936.JavaMail.root@redhat.com>
	<87sj784ugp.fsf@fimbulvetr.bsc.es>
In-Reply-To: <87sj784ugp.fsf@fimbulvetr.bsc.es>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH] build: Use separate makefile for "trace/"
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-15?Q?Llu=EDs_Vilanova?= <vilanova@ac.upc.edu>
Cc: qemu-devel@nongnu.org

Il 14/12/2012 14:46, Llu=EDs Vilanova ha scritto:
>>> The thing I like about automake is that it provides a clear set of va=
rs to
>>> manage the per-dir builds, thanks to using a per-dir $(MAKE); but I'm
>>> not sure how the per-target build would be managed (except by having =
a
>>> separate configure+make for each of them).
>>> Yes, that would be it.
>=20
> I'd certainly love to see something along those lines for the sake of m=
akefile
> simplicity.

QEMU is complex enough that I'm not really sure what Automake would buy.

>> > Even an autoconf conversion probably would have to use separate conf=
igure
>> > scripts for the global project and for each target.
> If you're willing to pay for a complete recompilation for each target y=
ou can
> just have a single configure file.

That's not the problem.  The problem is that Autoconf does not lend well
to the style of the QEMU build system, with many subparts that are
enabled/disabled at configure time.

> Ah, I know that one in gcc=20
>=20
>   -Wl,--whole-archive foo.a -Wl,--no-whole-archive

Really in ld (that's what -Wl does) and not very portable...

Paolo