From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>,
Luiz Capitulino <lcapitulino@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-1.1] Makefile: Fix QOM dependencies
Date: Sun, 27 May 2012 03:01:13 +0200 [thread overview]
Message-ID: <4FC17CD9.4020904@suse.de> (raw)
In-Reply-To: <1338078550-22119-1-git-send-email-afaerber@suse.de>
Am 27.05.2012 02:29, schrieb Andreas Färber:
> Dependency files qom/*.d were not included by Makefile, causing changes
> in object.h (e.g., changes to struct Object) not to propagate to
> qom-qobject.o, container.o and cpu.o. Add qom/*.d to the wildcard list.
>
> libuser/qom/cpu.o was unaffected since Makefile.user includes */*.d.
>
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
> Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 9b7a85e..0bb0529 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -400,4 +400,4 @@ tar:
> rm -rf /tmp/$(FILE)
>
> # Include automatically generated dependency files
> --include $(wildcard *.d audio/*.d slirp/*.d block/*.d net/*.d ui/*.d qapi/*.d qga/*.d)
> +-include $(wildcard *.d audio/*.d slirp/*.d block/*.d net/*.d ui/*.d qapi/*.d qga/*.d qom/*.d)
I wonder if, independently of QOM, we also need to consider...
- qapi-generated/*.d,
- usb/*.d and
- tests/*.d?
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-05-27 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 0:29 [Qemu-devel] [PATCH for-1.1] Makefile: Fix QOM dependencies Andreas Färber
2012-05-27 1:01 ` 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=4FC17CD9.4020904@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=lcapitulino@redhat.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).