From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <jbeulich@suse.com>,
Andrii Anisov <Andrii_Anisov@epam.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: [Xen-devel] [PATCH v1 1/2] makefile: add support for *_defconfig targets
Date: Tue, 14 May 2019 18:45:56 +0000 [thread overview]
Message-ID: <20190514184552.25100-1-volodymyr_babchuk@epam.com> (raw)
Message-ID: <20190514184556.lCX_bHcnB6G2wC7fqOuNBoLg5hoFg1bvuJ0v8myjFHM@z> (raw)
Ease up XEN configuration for non-standard builds, like
armv8 tiny config.
Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
---
Makefile | 4 ++++
xen/Makefile | 3 +++
2 files changed, 7 insertions(+)
diff --git a/Makefile b/Makefile
index 829ac63741..ef1ea44ef1 100644
--- a/Makefile
+++ b/Makefile
@@ -54,6 +54,10 @@ build: $(TARGS_BUILD)
build-xen:
$(MAKE) -C xen build
+.PHONY: %_defconfig
+%_defconfig:
+ $(MAKE) -C xen $@
+
.PHONY: build-tools
build-tools: build-tools-public-headers
$(MAKE) -C tools build
diff --git a/xen/Makefile b/xen/Makefile
index 1fd8ad5116..3c7e423132 100644
--- a/xen/Makefile
+++ b/xen/Makefile
@@ -269,6 +269,9 @@ kconfig := silentoldconfig oldconfig config menuconfig defconfig \
$(kconfig):
$(MAKE) -f $(BASEDIR)/tools/kconfig/Makefile.kconfig ARCH=$(ARCH) SRCARCH=$(SRCARCH) HOSTCC="$(HOSTCC)" HOSTCXX="$(HOSTCXX)" $@
+%_defconfig:
+ $(MAKE) -f $(BASEDIR)/tools/kconfig/Makefile.kconfig ARCH=$(ARCH) SRCARCH=$(SRCARCH) HOSTCC="$(HOSTCC)" HOSTCXX="$(HOSTCXX)" $@
+
include/config/%.conf: include/config/auto.conf.cmd $(KCONFIG_CONFIG)
$(MAKE) -f $(BASEDIR)/tools/kconfig/Makefile.kconfig ARCH=$(ARCH) SRCARCH=$(SRCARCH) HOSTCC="$(HOSTCC)" HOSTCXX="$(HOSTCXX)" silentoldconfig
--
2.21.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-05-14 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 18:45 Volodymyr Babchuk [this message]
2019-05-14 18:45 ` [Xen-devel] [PATCH v1 1/2] makefile: add support for *_defconfig targets Volodymyr Babchuk
2019-05-14 18:45 ` [PATCH v1 2/2] arm: rename tiny64.conf to tiny64_defconfig Volodymyr Babchuk
2019-05-14 18:45 ` [Xen-devel] " Volodymyr Babchuk
2019-05-15 7:24 ` [PATCH v1 1/2] makefile: add support for *_defconfig targets Jan Beulich
2019-05-15 7:24 ` [Xen-devel] " Jan Beulich
2019-05-15 19:07 ` Volodymyr Babchuk
2019-05-15 19:07 ` [Xen-devel] " Volodymyr Babchuk
2019-05-16 7:21 ` Jan Beulich
2019-05-16 7:21 ` [Xen-devel] " Jan Beulich
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=20190514184552.25100-1-volodymyr_babchuk@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=Andrii_Anisov@epam.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).