From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] make: automatically include dependencies in recursive subdir rules
Date: Sun, 17 Jun 2012 19:06:48 -0500 [thread overview]
Message-ID: <4FDE7118.7060909@codemonkey.ws> (raw)
In-Reply-To: <4FDE35D4.2050109@suse.de>
On 06/17/2012 02:53 PM, Andreas Färber wrote:
> Am 17.06.2012 20:46, schrieb Anthony Liguori:
>> On 06/17/2012 12:00 PM, Andreas Färber wrote:
>>> If using hw/kvm/*.d instead, it actually works. ;)
>>
>> We can also just add a hw/kvm/Makefile.objs and then add kvm/ to the
>> subdir rules. Seems to fix the problem you identified.
>
> No, that would be wrong wrt ppc/s390/arm. But we could move the files
> from hw/kvm/ to hw/i386/.
Hrm, no, I don't think that's necessary.
Look at v2 of my patch. kvm/ is only added by target hw makefiles
(hw/i386/Makefile.objs). So these devices are only even attempted to be added
for i386.
Then within kvm/Makefile.objs, everything is guarded with CONFIG_KVM.
I think a better approach would be to:
hw/Makefiles.obj:
obj-$(CONFIG_KVM) += kvm/
hw/kvm/Makefiles.obj:
obj-$(CONFIG_I386) += apic.o pit.o ...
That way there could be ppc-specific KVM devices.
But that's a bigger refactoring as these devices need to be built target-specific.
Regards,
Anthony Liguori
>
> Andreas
>
next prev parent reply other threads:[~2012-06-18 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 14:57 [Qemu-devel] [PATCH] make: automatically include dependencies in recursive subdir rules Anthony Liguori
2012-06-17 15:20 ` Blue Swirl
2012-06-17 16:23 ` Andreas Färber
2012-06-17 17:00 ` Andreas Färber
2012-06-17 18:46 ` Anthony Liguori
2012-06-17 19:53 ` Andreas Färber
2012-06-18 0:06 ` Anthony Liguori [this message]
2012-06-17 15:33 ` Andreas Färber
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=4FDE7118.7060909@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=blauwirbel@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).