From: Christopher Clark <christopher.w.clark@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com, jbeulich@suse.com
Subject: [PATCH v3] firmware/shim : filter output files during Xen tree setup
Date: Thu, 26 Jul 2018 14:16:46 -0700 [thread overview]
Message-ID: <1532639806-21606-1-git-send-email-christopher.w.clark@gmail.com> (raw)
Exclude named output files from the Xen tree setup.
The linkfarm.stamp content will differ between top level "make"
and "make install" invocations, due to the introduction of these
output files that are produced during the "make" build.
Filter these out to prevent an unnecessary rebuild of the shim
during "make install", after "make" within a fresh source tree.
Excluded from consideration with this change: differences in stamp
content when performing incremental builds in an existing tree.
Signed-off-by: Christopher Clark <christopher.clark6@baesystems.com>
---
Changes in v3: added '.xen.efi.*' '.xen-syms.*' to the exclude list.
Tested with: Xen 4.10.1, 4.11.0 and staging,
Yocto poky, OpenEmbedded meta-openembedded, meta-virtualization
with binutils 2.3.0 with x86_64-pep target enabled.
tools/firmware/xen-dir/Makefile | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/firmware/xen-dir/Makefile b/tools/firmware/xen-dir/Makefile
index 84648c3..af789d0 100644
--- a/tools/firmware/xen-dir/Makefile
+++ b/tools/firmware/xen-dir/Makefile
@@ -11,6 +11,11 @@ D=xen-root
LINK_DIRS=config xen
LINK_FILES=Config.mk
+# Files to exclude from the link farm
+EXCLUDE_FILES=xen xen.gz xen-syms xen-syms.map xen.efi xen.efi.map \
+ efi.lds xen.lds mkelf32 mkreloc \
+ '.xen.efi.*' '.xen-syms.*'
+
DEP_DIRS=$(foreach i, $(LINK_DIRS), $(XEN_ROOT)/$(i))
DEP_FILES=$(foreach i, $(LINK_FILES), $(XEN_ROOT)/$(i))
@@ -26,7 +31,8 @@ linkfarm.stamp: $(DEP_DIRS) $(DEP_FILES) FORCE
$(foreach d, $(LINK_DIRS), \
(cd $(XEN_ROOT); \
find $(d) ! -type l -type f \
- $(addprefix ! -name , '*.[isoa]' '.*.d' '.*.d2')) \
+ $(addprefix ! -name , '*.[isoa]' '.*.d' '.*.d2' \
+ $(EXCLUDE_FILES) )) \
>> linkfarm.stamp.tmp ; ) \
$(foreach f, $(LINK_FILES), \
echo $(f) >> linkfarm.stamp.tmp ;)
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-07-26 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 21:16 Christopher Clark [this message]
2018-07-27 8:34 ` [PATCH v3] firmware/shim : filter output files during Xen tree setup Jan Beulich
2018-07-30 1:22 ` Christopher Clark
2018-07-30 8:31 ` 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=1532639806-21606-1-git-send-email-christopher.w.clark@gmail.com \
--to=christopher.w.clark@gmail.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--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 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.