From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org, peter.maydell@linaro.org, mjt@tls.msk.ru,
stefanha@redhat.com, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [RFC PATCH v2 1/6] make.rule: fix $(obj) to a real relative path
Date: Mon, 9 Sep 2013 09:34:50 +0800 [thread overview]
Message-ID: <20130909013450.GA23625@T430s.nay.redhat.com> (raw)
In-Reply-To: <87zjrp98bq.fsf@fimbulvetr.bsc.es>
On Fri, 09/06 20:19, Lluís Vilanova wrote:
> Fam Zheng writes:
> [...]
> > Because $(obj) here is './block', instead of '../block'. This doesn't
> > hurt compiling because we basically build all .o from top Makefile,
> > before entering Makefile.target, but it will affact arriving per-object
> > libs support.
>
> I'm curious. What's the reason to not use recursive make in QEMU?
>
I don't know the answer, Paolo?
Fam
next prev parent reply other threads:[~2013-09-09 1:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 7:28 [Qemu-devel] [RFC PATCH v2 0/6] Shared Library Module Support Fam Zheng
2013-09-06 7:28 ` [Qemu-devel] [RFC PATCH v2 1/6] make.rule: fix $(obj) to a real relative path Fam Zheng
2013-09-06 17:19 ` Lluís Vilanova
2013-09-09 1:34 ` Fam Zheng [this message]
2013-09-09 10:41 ` Paolo Bonzini
2013-09-09 10:46 ` Peter Maydell
2013-09-06 7:28 ` [Qemu-devel] [RFC PATCH v2 2/6] rule.mak: allow per object cflags and libs Fam Zheng
2013-09-06 10:42 ` Michael Tokarev
2013-09-06 10:52 ` Fam Zheng
2013-09-06 7:28 ` [Qemu-devel] [RFC PATCH v2 3/6] Makefile: introduce common-obj-m and block-obj-m for DSO Fam Zheng
2013-09-06 10:09 ` Paolo Bonzini
2013-09-06 11:47 ` Fam Zheng
2013-09-06 12:11 ` Paolo Bonzini
2013-09-09 2:26 ` Fam Zheng
2013-09-09 10:43 ` Paolo Bonzini
2013-09-06 7:28 ` [Qemu-devel] [RFC PATCH v2 4/6] module: implement module loading function Fam Zheng
2013-09-06 9:47 ` Paolo Bonzini
2013-09-06 7:28 ` [Qemu-devel] [RFC PATCH v2 5/6] curl: build as shared library Fam Zheng
2013-09-06 7:28 ` [Qemu-devel] [RFC PATCH v2 6/6] qed: " Fam Zheng
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=20130909013450.GA23625@T430s.nay.redhat.com \
--to=famz@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.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).