From: Peter Maydell <peter.maydell@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] make: remove generated objects from target dirs
Date: Sun, 4 Mar 2012 13:25:59 +0000 [thread overview]
Message-ID: <CAFEAcA8MWg4Eh+pTPN1ZjJQphc_1gd6T8DbSYhQi0trivYYc0w@mail.gmail.com> (raw)
In-Reply-To: <20120304091007.GA2252@redhat.com>
On 4 March 2012 09:10, Michael S. Tsirkin <mst@redhat.com> wrote:
> I ended up with qmp-commands.h in target directories,
> which makes build fail as it is found before the
> main header.
> make clean fixes it, but it might get triggered
> again when we make some header target-independent next.
> It's easy to just make sure all such leftovers are
> removed, so let's do this.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>
> diff --git a/Makefile b/Makefile
> index e66e885..958a414 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -89,6 +89,7 @@ qemu-options.def: $(SRC_PATH)/qemu-options.hx
> SUBDIR_RULES=$(patsubst %,subdir-%, $(TARGET_DIRS))
>
> subdir-%: $(GENERATED_HEADERS)
> + $(call quiet-command,rm -f $(foreach header, $(GENERATED_HEADERS), "$*/$(header)"),)
> $(call quiet-command,$(MAKE) $(SUBDIR_MAKEFLAGS) -C $* V="$(V)" TARGET_DIR="$*/" all,)
In general we don't have workarounds for "something
moved directory and this broke builds not from clean"
(source file moved from hw/ to . being one that's bitten
me before), so why does just this one deserve to get an
rm here rather than just asking the user to run
'make clean / distclean' ?
-- PMM
next prev parent reply other threads:[~2012-03-04 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 9:10 [Qemu-devel] [PATCH] make: remove generated objects from target dirs Michael S. Tsirkin
2012-03-04 13:25 ` Peter Maydell [this message]
2012-03-04 13:31 ` Michael S. Tsirkin
2012-03-04 13:44 ` Peter Maydell
2012-03-04 14:13 ` Michael S. Tsirkin
2012-03-04 16:03 ` Andreas Färber
2012-03-04 16:49 ` Michael S. Tsirkin
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=CAFEAcA8MWg4Eh+pTPN1ZjJQphc_1gd6T8DbSYhQi0trivYYc0w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=anthony@codemonkey.ws \
--cc=mst@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).