From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>
Subject: tools/makefile: Add build target
Date: Wed, 1 Aug 2012 19:22:45 +0100 [thread overview]
Message-ID: <501973F5.4030804@citrix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
The alternative is to change the root makefile to call "$(MAKE) -C
tools/ all" instead, but this way feels neater to me.
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
[-- Attachment #2: tools-build-target.patch --]
[-- Type: text/x-patch, Size: 688 bytes --]
# HG changeset patch
# Parent f8ea2e12ed5ab33f160e65f22c9ce8f379863053
tools/makefile: Add build target
The root Makefile has a build target which calls "$(MAKE) build" in each of xen/
tools/ stubdom/ and docs/, which fails because of the tools/ Makefile.
This patch adds a phony build target, allowing a call to "make build" in the
repository root directory still work.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
diff -r f8ea2e12ed5a tools/Makefile
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -64,6 +64,9 @@ endif
.PHONY: all
all: subdirs-all
+.PHONY: build
+build: subdirs-all
+
.PHONY: install
install: subdirs-install
$(INSTALL_DIR) $(DESTDIR)/var/xen/dump
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-08-01 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 18:22 Andrew Cooper [this message]
2012-08-07 18:27 ` tools/makefile: Add build target Ian Jackson
2012-08-08 9:45 ` Andrew Cooper
2012-08-09 16:59 ` Ian Jackson
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=501973F5.4030804@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=ian.jackson@eu.citrix.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.