summaryrefslogtreecommitdiff
path: root/CryptoPkg
diff options
context:
space:
mode:
authorDerek Lin <derek.lin2@hpe.com>2017-02-24 15:26:19 +0800
committerYonghong Zhu <yonghong.zhu@intel.com>2017-03-25 12:13:01 +0800
commitc17956e0eedce299ac253ac40238ce90a5e623e0 (patch)
tree5298c2b9b678bf437e3a1f1a5213376571288218 /CryptoPkg
parent647636e1750b07110ed807f455cb9c8b7d089f75 (diff)
downloadedk2-c17956e0eedce299ac253ac40238ce90a5e623e0.zip
edk2-c17956e0eedce299ac253ac40238ce90a5e623e0.tar.gz
edk2-c17956e0eedce299ac253ac40238ce90a5e623e0.tar.bz2
BaseTools: Skip module AutoGen by comparing timestamp.
[Introduction] The BaseTool Build.py AutoGen parse INF meta-file and generate AutoGen.c/AutoGen.h/makefile. When we only change .c .h code, the AutoGen might be not necessary, but Build.py spend a lot of time on it. There's a -u flag to skip all module's AutoGen. In my environment, it save 35%~50% of time in rebuild a ROM. However, if user change one .INF meta-file, then -u flag is not available. [Idea] AutoGen can compare meta-file's timestamp and decide if the module's AutoGen can be skipped. With this, when a module's INF is changed, we only run this module's AutoGen, we don't need to run other module's. [Implementation] In the end of a module's AutoGen, we create a AutoGenTimeStamp. The file save a file list that related to this module's AutoGen. In other word, the file list in AutoGenTimeStamp is INPUT files of module AutoGen, AutoGenTimeStamp file is OUTPUT. During rebuild, we compare time stamp between INPUT and OUTPUT, and decide if we can skip it. Below is the Input/Output of a module's AutoGen. [Input] 1. All the DSC/DEC/FDF used by the platform. 2. Macro and PCD defined by Build Options such as "build -D AAA=TRUE --pcd BbbPcd=0". 3. INF file of a module. 4. Source files of a module, list in [Sources] section of INF. 5. All the library link by the module. 6. All the .h files included by the module's sources. [Output] AutoGen.c/AutoGen.h/makefile/AutoGenTimeStamp [Testing] This patch save my build time. When I make a change without touching DSC/DEC/FDF, it is absolutely much faster than original rebuild, 35%~50% time saving in my environment (compare to original tool rebuild time). If I change any DSC/DEC/FDF, there's no performance improve, because it can't skip any module's AutoGen. Please note that if your environment will generate DSC/FDF during prebuild, it will not skip any AutoGen because of DSC timestamp is changed. This will require prebuild script not to update metafile when content is not changed.
Diffstat (limited to 'CryptoPkg')
0 files changed, 0 insertions, 0 deletions