From nobody Tue Dec 24 16:47:08 2024 Delivered-To: importer@patchew.org Authentication-Results: mx.zohomail.com; spf=none (zoho.com: 198.145.21.10 is neither permitted nor denied by domain of lists.01.org) smtp.mailfrom=edk2-devel-bounces@lists.01.org Return-Path: Received: from ml01.01.org (ml01.01.org [198.145.21.10]) by mx.zohomail.com with SMTPS id 1512359132811389.10650848434557; Sun, 3 Dec 2017 19:45:32 -0800 (PST) Received: from [127.0.0.1] (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id 4B53E220EE076; Sun, 3 Dec 2017 19:41:02 -0800 (PST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id AFFF0220EE073 for ; Sun, 3 Dec 2017 19:41:01 -0800 (PST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Dec 2017 19:45:30 -0800 Received: from shwdeopenpsi168.ccr.corp.intel.com ([10.239.158.129]) by orsmga002.jf.intel.com with ESMTP; 03 Dec 2017 19:45:29 -0800 X-Original-To: edk2-devel@lists.01.org Received-SPF: none (zoho.com: 198.145.21.10 is neither permitted nor denied by domain of lists.01.org) client-ip=198.145.21.10; envelope-from=edk2-devel-bounces@lists.01.org; helo=ml01.01.org; Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.93; helo=mga11.intel.com; envelope-from=yonghong.zhu@intel.com; receiver=edk2-devel@lists.01.org X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,357,1508828400"; d="scan'208";a="14991975" From: Yonghong Zhu To: edk2-devel@lists.01.org Date: Mon, 4 Dec 2017 11:45:26 +0800 Message-Id: <1512359126-10900-1-git-send-email-yonghong.zhu@intel.com> X-Mailer: git-send-email 2.6.1.windows.1 Subject: [edk2] [Patch] Build spec: Add clarification for the binary cache files X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Michael Kinney , Kevin W Shaw , Liming Gao MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Errors-To: edk2-devel-bounces@lists.01.org Sender: "edk2-devel" X-ZohoMail: RSF_4 Z_629925259 SPT_0 Content-Type: text/plain; charset="utf-8" Add clarification for the detail files that would be copied into the directory specified by --binary-destination. Cc: Liming Gao Cc: Michael Kinney Cc: Kevin W Shaw Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Yonghong Zhu Reviewed-by: Liming Gao --- 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_pr= e-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 co= mbine 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 t= he generated -binary files for each module into the directory specified by binary-destin= ation at the -build phase. Binary-destination directory caches all the generated binary = files. +When --hash and --binary-destination are specified, build tool will copy e= ach 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 b= inary has the same hash value, it will be directly used. Otherwise, build tool will = compile the source files and generate the binary files. =20 --=20 2.6.1.windows.1 _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel