All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: dead qemu make targets in toplevel Makefile
Date: Tue, 7 Oct 2014 14:16:08 +0100	[thread overview]
Message-ID: <1412687768.4972.22.camel@citrix.com> (raw)
In-Reply-To: <20141007130727.GA5984@aepfle.de>

On Tue, 2014-10-07 at 15:07 +0200, Olaf Hering wrote:
> Ian,
> 
> with commit b0f69ec5c71de1248d915c193b57c43e786857dd ("tools: Make
> qemu-xen-traditional build optional.") the existing make targets are
> wrapped in ifeq ($(CONF),y), but CONF is never set because
> config/Tools.mk is not included. I wonder if that ever worked or if I
> just broke it with my changes. But looking at 4.4.1 I dont see how
> CONFIG_QEMU_TRAD is set. And in staging QEMU_TRAD_DIR_TGT is also not
> used.
> 
> Are these make targets useful? I see "git clean -dfx && ./configure &&
> make tools/qemu-xen-traditional-dir CONFIG_QEMU_TRAD=y" clones the tree.

I think they were just intended as a convenient shortcut to allow
updating the cloned trees (which are otherwise not automatically
updated). I'm not sure how useful they are in practice.

It looks like my build scripts use "make -C tools $FOO-force-update", so
removing them would be a problem for me personally.

On the other hand since they are only for use by end users and not
dependencies of any other rule I suppose we could just nuke the
conditionals but leave the rules themselves?

Ian.

  reply	other threads:[~2014-10-07 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 13:07 dead qemu make targets in toplevel Makefile Olaf Hering
2014-10-07 13:16 ` Ian Campbell [this message]
2014-10-07 13:26   ` Olaf Hering
2014-10-07 13:28     ` Ian Campbell

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=1412687768.4972.22.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.