From: Paolo Bonzini <pbonzini@redhat.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] build: Use separate makefile for "trace/"
Date: Fri, 14 Dec 2012 14:50:20 +0100 [thread overview]
Message-ID: <50CB2E9C.4010600@redhat.com> (raw)
In-Reply-To: <87sj784ugp.fsf@fimbulvetr.bsc.es>
Il 14/12/2012 14:46, Lluís Vilanova ha scritto:
>>> The thing I like about automake is that it provides a clear set of vars 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.
>
> I'd certainly love to see something along those lines for the sake of makefile
> 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 configure
>> > scripts for the global project and for each target.
> If you're willing to pay for a complete recompilation for each target you 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
>
> -Wl,--whole-archive foo.a -Wl,--no-whole-archive
Really in ld (that's what -Wl does) and not very portable...
Paolo
next prev parent reply other threads:[~2012-12-14 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 21:44 [Qemu-devel] [PATCH] build: Use separate makefile for "trace/" Lluís Vilanova
2012-12-12 8:43 ` Paolo Bonzini
2012-12-12 14:53 ` Lluís Vilanova
2012-12-13 8:44 ` Paolo Bonzini
2012-12-13 14:38 ` Lluís Vilanova
2012-12-14 8:14 ` Paolo Bonzini
2012-12-14 13:46 ` Lluís Vilanova
2012-12-14 13:50 ` Paolo Bonzini [this message]
2012-12-14 15:04 ` Lluís Vilanova
-- strict thread matches above, loose matches on Subject: below --
2012-12-11 21:49 Lluís Vilanova
2012-12-14 18:34 Lluís Vilanova
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=50CB2E9C.4010600@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.