From: Anthony PERARD <anthony.perard@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Doug Goldstein <cardoe@cardoe.com>, Wei Liu <wl@xen.org>
Subject: [Xen-devel] [XEN PATCH 1/2] tools: Allow to make *-dir-force-update without ./configure
Date: Thu, 19 Dec 2019 14:42:16 +0000 [thread overview]
Message-ID: <20191219144217.305851-2-anthony.perard@citrix.com> (raw)
In-Reply-To: <20191219144217.305851-1-anthony.perard@citrix.com>
This also allows to run `make src-tarball` without first having to run
`./configure`.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
---
tools/Rules.mk | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/Rules.mk b/tools/Rules.mk
index cf8935d6a3ea..31cf419ef4f5 100644
--- a/tools/Rules.mk
+++ b/tools/Rules.mk
@@ -239,7 +239,8 @@ subdir-all-% subdir-clean-% subdir-install-% subdir-uninstall-%: .phony
subdir-distclean-%: .phony
$(MAKE) -C $* distclean
-ifeq (,$(findstring clean,$(MAKECMDGOALS)))
+no-configure-targets := clean subtree-force-update-all %-dir-force-update
+ifeq (,$(filter $(no-configure-targets),$(MAKECMDGOALS)))
$(XEN_ROOT)/config/Tools.mk:
$(error You have to run ./configure before building or installing the tools)
endif
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-19 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 14:42 [Xen-devel] [XEN PATCH 0/2] Start using GitLab caching capability Anthony PERARD
2019-12-19 14:42 ` Anthony PERARD [this message]
2020-01-03 14:24 ` [Xen-devel] [XEN PATCH 1/2] tools: Allow to make *-dir-force-update without ./configure Wei Liu
2019-12-19 14:42 ` [Xen-devel] [XEN PATCH 2/2] automation: Cache sub-project git tree in build jobs Anthony PERARD
2020-01-03 14:29 ` Wei Liu
2020-01-06 14:34 ` Anthony PERARD
2020-01-08 16:07 ` Wei Liu
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=20191219144217.305851-2-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.