From: Ben Thomas <bthomas@virtualiron.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH][TOOLS] - allow python tools build to be optional
Date: Tue, 06 Mar 2007 11:29:48 -0500 [thread overview]
Message-ID: <45ED96FC.7070700@virtualiron.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
This patch adds the python tools to the potential set of selectable
items within a tools build. The default remains to build the tools,
and the patch simply allows the specification of PYTHON_TOOLS=n
to omit building them.
--
------------------------------------------------------------------------
Ben Thomas Virtual Iron Software
bthomas@virtualiron.com Tower 1, Floor 2
978-849-1214 900 Chelmsford Street
Lowell, MA 01851
[-- Attachment #2: tools-python_optional.patch --]
[-- Type: text/x-patch, Size: 932 bytes --]
Several of the components of tools are optional, allow the
python tools to be optional as well. The default, however,
remains to include them.
Signed-off-by: Ben Thomas (ben@virtualiron.com)
diff -r 277d4a0d0cdf Config.mk
--- a/Config.mk Tue Mar 06 09:29:25 2007 -0500
+++ b/Config.mk Tue Mar 06 10:55:39 2007 -0500
@@ -77,5 +77,6 @@ VTPM_TOOLS ?= n
VTPM_TOOLS ?= n
LIBXENAPI_BINDINGS ?= n
XENFB_TOOLS ?= n
+PYTHON_TOOLS ?= y
-include $(XEN_ROOT)/.config
diff -r 277d4a0d0cdf tools/Makefile
--- a/tools/Makefile Tue Mar 06 09:29:25 2007 -0500
+++ b/tools/Makefile Tue Mar 06 10:57:36 2007 -0500
@@ -24,9 +24,9 @@ SUBDIRS-$(LIBXENAPI_BINDINGS) += libxen
# These don't cross-compile
ifeq ($(XEN_COMPILE_ARCH),$(XEN_TARGET_ARCH))
-SUBDIRS-y += python
-SUBDIRS-y += pygrub
-SUBDIRS-y += ptsname
+SUBDIRS-$(PYTHON_TOOLS) += python
+SUBDIRS-$(PYTHON_TOOLS) += pygrub
+SUBDIRS-$(PYTHON_TOOLS) += ptsname
endif
.PHONY: all
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2007-03-06 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45ED96FC.7070700@virtualiron.com \
--to=bthomas@virtualiron.com \
--cc=xen-devel@lists.xensource.com \
/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.