public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Shaw, Kevin W" <kevin.w.shaw@intel.com>
Subject: Re: [Patch] Build spec: Add clarification for the binary cache files
Date: Mon, 11 Dec 2017 02:32:53 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E18E5BD@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1512359126-10900-1-git-send-email-yonghong.zhu@intel.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: Zhu, Yonghong
>Sent: Monday, December 04, 2017 11:45 AM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming <liming.gao@intel.com>; Kinney, Michael D
><michael.d.kinney@intel.com>; Shaw, Kevin W <kevin.w.shaw@intel.com>
>Subject: [Patch] Build spec: Add clarification for the binary cache files
>
>Add clarification for the detail files that would be copied into the
>directory specified by --binary-destination.
>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Michael Kinney <michael.d.kinney@intel.com>
>Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
>---
> 8_pre-build_autogen_stage/82_auto-generation_process.md | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
>diff --git a/8_pre-build_autogen_stage/82_auto-generation_process.md
>b/8_pre-build_autogen_stage/82_auto-generation_process.md
>index f2ddf32..f610185 100644
>--- a/8_pre-build_autogen_stage/82_auto-generation_process.md
>+++ b/8_pre-build_autogen_stage/82_auto-generation_process.md
>@@ -1043,13 +1043,13 @@ option use md5 method to get every hash value,
>DSC/FDF, tools_def.txt, build_rul
> and build command are calculated as global hash value, Package DEC and its
>include
> header files are calculated as package hash value, Module source files and its
>INF
> file are calculated as module hash value. Library hash value will combine the
>global
> hash value and its dependent package hash value. Driver hash value will
>combine the
> global hash value, its dependent package hash value and its linked library
>hash value.
>-When --hash and --binary-destination are specified, build tool will copy the
>generated
>-binary files for each module into the directory specified by binary-destination
>at the
>-build phase. Binary-destination directory caches all the generated binary files.
>+When --hash and --binary-destination are specified, build tool will copy each
>module's
>+"As Built" inf file, binary files that in "As built" inf file's [Binaries] section and
>+hash value file into the directory specified by binary-destination at the build
>phase.
> When --hash and --binary-source are specified, build tool will try to get the
>binary
> files from the binary source directory at the build phase. If the cached binary
>has
> the same hash value, it will be directly used. Otherwise, build tool will compile
>the
> source files and generate the binary files.
>
>--
>2.6.1.windows.1



      reply	other threads:[~2017-12-11  2:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04  3:45 [Patch] Build spec: Add clarification for the binary cache files Yonghong Zhu
2017-12-11  2:32 ` Gao, Liming [this message]

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-list 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E18E5BD@SHSMSX104.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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