From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 1/2] make: Check tools/qemu-xen[-traditional] for qemu before downloading
Date: Thu, 3 Jul 2014 10:04:06 +0100 [thread overview]
Message-ID: <53B51C86.20502@eu.citrix.com> (raw)
In-Reply-To: <1404375913.11440.6.camel@kazak.uk.xensource.com>
On 07/03/2014 09:25 AM, Ian Campbell wrote:
> On Wed, 2014-07-02 at 17:15 +0100, George Dunlap wrote:
>> Currently xen, qemu-xen, and qemu-xen-traditional are kept in separate
>> repositories, but when we release them as a tarball, qemu-xen and
>> qemu-xen-traditional are in-lined into the tools/ directory.
>>
>> In order to make this "just work", at the moment developer doing the
>> release manually modifies Config.mk as part of the relase process so
>> that CONFIG_QEMU and QEMU_UPSTREAM_URL point into the tools/ directory
>> instead.
> Since this mainly means Ian I'll mostly leave both of these patches to
> him.
>
>> +# Specify which qemu-dm to use. This may be `ioemu' to use the old
>> +# Mercurial in-tree version, or a local directory, or a git URL.
>> +# CONFIG_QEMU ?= `pwd`/$(XEN_ROOT)/../qemu-xen.git
>> +ifneq (,$(wildcard $(XEN_ROOT)/tools/qemu-xen-traditional))
>> +CONFIG_QEMU ?= $(XEN_ROOT)/tools/qemu-xen-traditional
>> +else
>> +CONFIG_QEMU ?= $(QEMU_REMOTE)
>> +endif
> Does this DTRT on subsequent runs after the automatic git clone has
> happened on the first run? I suspect so, but I'm not 100% sure. f.e.
> does "make tools/qemu-xen-traditional-dir-force-update" still work?
Yes, all that still works, because the directories it creates when
automatically cloning the qemu repos are named differently
(qemu-xen[-traditional]-dir[-remote]).
-George
next prev parent reply other threads:[~2014-07-03 9:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 16:15 [PATCH 1/2] make: Check tools/qemu-xen[-traditional] for qemu before downloading George Dunlap
2014-07-02 16:15 ` [PATCH 2/2] make: Make "src-tarball" target actually make a source tarball George Dunlap
2014-07-03 8:29 ` Ian Campbell
2014-07-03 12:48 ` George Dunlap
2014-07-03 13:46 ` Ian Campbell
2014-07-08 9:50 ` Ian Jackson
2014-07-08 11:00 ` George Dunlap
2014-07-03 11:22 ` Anthony PERARD
2014-07-03 11:25 ` George Dunlap
2014-07-03 8:25 ` [PATCH 1/2] make: Check tools/qemu-xen[-traditional] for qemu before downloading Ian Campbell
2014-07-03 9:04 ` George Dunlap [this message]
2014-07-03 9:10 ` Ian Campbell
2014-07-08 9:57 ` Ian Jackson
2014-07-08 10:57 ` George Dunlap
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=53B51C86.20502@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--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.