diff options
author | Pierre Gondois <pierre.gondois@arm.com> | 2020-02-10 18:49:07 +0800 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2020-02-12 02:34:44 +0000 |
commit | 818283de3f6d3b288deda54f0734be5bb70ddd5a (patch) | |
tree | ba30c9f6974f183d5db7aeadb8a4893e9330d85d /BaseTools/Source/Python/Ecc | |
parent | e465aae055258457e91ce2d3fef87d25507c5b24 (diff) | |
download | edk2-818283de3f6d3b288deda54f0734be5bb70ddd5a.tar.gz edk2-818283de3f6d3b288deda54f0734be5bb70ddd5a.tar.bz2 edk2-818283de3f6d3b288deda54f0734be5bb70ddd5a.zip |
BaseTools: Rationalise makefile generation
The GenMake.py script tests the platform environment
to determine the type of makefile that needs to be
generated. If a Windows build host is detected, the
makefile generated is of Nmake type. Otherwise a
GNUmake type is generated.
Furthermore, the <TARGET>_<TAGNAME>_<ARCH>_MAKE_PATH
option in tools_def.template defines the make tool
to use.
E.g.: for VS2017 this is configured to use Nmake, cf.
*_VS2017_*_MAKE_PATH = DEF(VS2017_BIN_HOST)\nmake.exe
while for GCC5 it is setup to use GNU make.
*_GCC5_*_MAKE_PATH = DEF(GCC_HOST_PREFIX)make
This prevents using the GCC compiler toolchain on a
Windows build host.
To address this issue this patch introduces 2 factors
to determine the generated makefile output.
1. Platform -> to determine shell commands used
in makefile.
2. MakeTool -> to determine the type of makefile
that needs to be generated.
Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
Signed-off-by: Sami Mujawar <sami.mujawar@arm.com>
Reviewed-by: Bob Feng <bob.c.feng@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Ecc')
0 files changed, 0 insertions, 0 deletions