From: "Andreas Färber" <afaerber@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] hw/Makefile.objs question
Date: Mon, 02 Jul 2012 14:11:55 +0200 [thread overview]
Message-ID: <4FF1900B.1010201@suse.de> (raw)
In-Reply-To: <4FF18FB9.7080904@ozlabs.ru>
Am 02.07.2012 14:10, schrieb Alexey Kardashevskiy:
> 02.07.2012 20:36, Paolo Bonzini пишет:
>> Il 21/06/2012 16:04, Andreas Färber ha scritto:
>>>
>>> *If* the file is built per target (hw/ppc64/Makefile.objs), then you can
>>> use *-softmmu/config-target.mak and just need to use a different
>>> Makefile than before.
>>>
>>> *If* the file is built per libhw (hw/Makefile.objs), then you need one
>>> option whether to compile it and another for whether to link it into a
>>> particular target.
>>
>> You only need the latter. Whether to compile it is decided by
>> config-all-devices.mak, but that file is automatically generated by
>> looking at all targets.
>
> At the moment, VFIO has #ifdef TARGET_PPC64 so it should be compiled per
> target, i.e. the first way. Or not?
Yes, I believe so.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-07-02 12:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 3:22 [Qemu-devel] hw/Makefile.objs question Alexey Kardashevskiy
2012-06-21 10:36 ` Andreas Färber
2012-06-21 11:21 ` Alexey Kardashevskiy
2012-06-21 12:19 ` Andreas Färber
2012-06-21 13:10 ` Alexey Kardashevskiy
2012-06-21 13:23 ` Anthony Liguori
2012-06-21 14:04 ` Andreas Färber
2012-06-21 15:52 ` Alex Williamson
2012-06-22 2:23 ` Alexey Kardashevskiy
2012-07-02 10:36 ` Paolo Bonzini
2012-07-02 12:10 ` Andreas Färber
2012-07-02 12:10 ` Alexey Kardashevskiy
2012-07-02 12:11 ` Andreas Färber [this message]
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=4FF1900B.1010201@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--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).