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

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

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

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel