Tianocore/edk2.git/BaseTools/Source/Python/build, branch edk2_masterEDK II (mirror)https://git.radix-linux.su/Tianocore/edk2.git/atom?h=edk2_master2026-01-06T04:44:08+00:00BaseTools/build: Add defines for Windows build environments2026-01-06T04:44:08+00:00Michael D Kinneymichael.d.kinney@intel.com2025-12-26T18:57:44+00:00urn:sha1:a0002ddc5342c7bb34fb3a0bb87c1235c8d8821d
The stuart tools automatically add -D WIN_HOST_BUILD to
edk2 build command line if a Windows build environment
is detected. This behavior is added to build.py so that
builds of the EmulatorPkg using build.py are not required
to add the option -D WIN_HOST_BUILD when building in a
Windows environment. This aligns Linux and Windows builds
of the EmulatorPkg removing the need to specify extra
defines.
In order to build the EmulatorPkg for Windows Mingw
environments, EmulatorPkg DSC/FDF files require a way
to detect if Windows Mingw environment is present.
The Windows Mingw environment can be detected if
CLANG_BIN is set and mingw32-make.exe is detected
in the CLANG_BIN directory.
If a Windows Mingw environment is detected, add
-D WIN_MINGW32_BUILD to the edk2 build command line.
Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
BaseTools: Cap AutoGen thread count to avoid file descriptor exhaustion2025-12-03T14:11:32+00:00Ayden Mengmengxiangdong@loongson.cn2025-11-27T12:57:59+00:00urn:sha1:a058a2856dec7d3e837ca5034fe892c83bc8077e
When the number of build threads multiplied by per-thread file
descriptor usage exceeds the system's open file descriptor limit,
some threads may fail to acquire necessary resources (e.g., pipes
or semaphores), leading to deadlocks or hangs during parallel builds.
To prevent this situation, calculate the safety upper limit of
concurrency by dividing the system's maximum file descriptor limit by
3 (An empirical value derived from balancing performance overhead
against the theoretical number of file descriptors consumed per thread).
The actual thread count is then clamped to this safe value.
Other usages of ThreadNum()—such as during actual compilation or log
queue creation—do not significantly contribute to file descriptor
consumption. Therefore, adjusting ThreadNum() globally would be
unwarranted, as it could unnecessarily restrict parallelism in stages
that are not FD-bound.
This ensures stable parallel builds even under constrained resource
limits.
Signed-off-by: Ayden Meng <mengxiangdong@loongson.cn>
BaseTools: Handle file descriptor exhaustion during parallel build2025-12-03T14:11:32+00:00Ayden Mengmengxiangdong@loongson.cn2025-11-27T11:55:31+00:00urn:sha1:7aaf742d2dc3f188b0307544cc767e6879df9c9e
Previously, when file descriptors were exhausted in high-concurrency
builds (e.g., 512 threads with 1024 FD limit), the build would hang or
fail silently without clear indication of the root cause.
This change catches relevant OSError instances and terminates the build,
ensuring failures due to resource limits are explicit.
Signed-off-by: Ayden Meng <mengxiangdong@loongson.cn>
BaseTools: Remove DXE_SAL_DRIVER2025-10-30T10:00:32+00:00Sathya Ravichandransathyar@ami.com2025-09-23T11:07:43+00:00urn:sha1:98d1f8a6fd94c32834087a8ecfc1cce7827496e7
The DXE_SAL_DRIVER module type was introduced to support
Itanium (IPF) platforms. Since support for Itanium processors has been
dropped, the instances of DXE_SAL_DRIVER have been removed.
Ref: [3cb0a311cb7e747d7be5c5076d0fff76ad256d2b]
Cc: Sachin Ganesh <sachinganesh@ami.com>
Signed-off-by: Sathya Ravichandran <sathyar@ami.com>
BaseTools/build.py: set BUILD_TIME_EPOCH if not already in environment2025-10-16T10:41:09+00:00Leif Lindholmleif.lindholm@oss.qualcomm.com2025-07-03T18:37:42+00:00urn:sha1:fcc568ca6e828c29bb85c76066cf89d3984a5fa3
Set BUILD_TIME_EPOCH to the current UTC timestamp if not already present
in the environment.
Use the resulting value to print the "Build start time:" message.
Signed-off-by: Leif Lindholm <leif.lindholm@oss.qualcomm.com>
BaseTools/build.py: language cleanup around CheckEnvVariable2025-10-16T10:41:09+00:00Leif Lindholmleif.lindholm@oss.qualcomm.com2025-07-03T17:30:43+00:00urn:sha1:5ca97bf64f6447d935210a54b422656f90e502ce
The function CheckEnvVariable in fact checks several environment
variables. And the comment at its invocation enumerates a specific set of
variables, which defeats half the point of abstracting it out into a
helper function.
Rename the function to the plural form and turn the comment into a list
of examples.
Signed-off-by: Leif Lindholm <leif.lindholm@oss.qualcomm.com>
BaseTools: Remove ARM32 Support2025-09-25T22:04:10+00:00Oliver Smith-Dennyosde@microsoft.com2025-09-17T21:24:49+00:00urn:sha1:2ff173af128e707867c6409f2e4ca308c255ca32
edk2 is dropping support for the ARM32 architecture. This
commit removes ARM32 code from BaseTools.
Signed-off-by: Oliver Smith-Denny <osde@microsoft.com>
BaseTools: Improve report generation for Nested Fvs.2025-07-08T02:06:36+00:00Aaron Popaaronpop@microsoft.com2025-07-01T18:36:18+00:00urn:sha1:0277d5d8f100f2490a08f3a7e38f08328283e4fe
Build report would not detect a nested FV if the nested
FV was not in a subsection of an FFS statement.
Modify the build report to better handle some of the
variations of nested FVs.
Failing Example:
[Fv.FvName1]
INF <path to some driver>.inf
[Fv.FvName0]
FILE FV_IMAGE = B25ACDEF-39CE-4FA5-B50A-33E24DB1BDDF {
SECTION FV_IMAGE = FvName1
}
Working Example:
[Fv.FvName1]
INF <path to some driver>.inf
[Fv.FvName0]
FILE FV_IMAGE = DA04F6BF-A0FD-47EC-928B-5101A6C95026 {
SECTION GUIDED EE4E5898-3914-4259-9D6E-DC7BD79403CF
PROCESSING_REQUIRED = TRUE {
SECTION FV_IMAGE = FvName1
}
}
Signed-off-by: Aaron Pop <aaronpop@microsoft.com>
BaseTools: build: Remove unnecessary code2025-07-01T01:51:38+00:00Pierre Gondoispierre.gondois@arm.com2025-04-30T12:31:24+00:00urn:sha1:ac9dc333965804e128945c28482c1b76199d6968
Running the vulture tool on the build folder gave the following
report. Remove the unnecessary code.
- build/build.py:79:
unused function 'IsToolInPath' (60% confidence)
- build/build.py:396:
unused class 'PlatformMakeUnit' (60% confidence)
- build/build.py:570:
unused method 'GetErrorMessage' (60% confidence)
- build/build.py:806:
unused attribute 'HashSkipModules' (60% confidence)
- build/build.py:807:
unused attribute 'Db_Flag' (60% confidence)
- build/build.py:1048:
unused attribute 'Db_Flag' (60% confidence)
- build/build.py:2500:
unused method 'GetRealPathOfTool' (60% confidence)
- build/BuildReport.py:1497:
unused method 'StrtoHex' (60% confidence)
Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
BaseTools: Remove unused import2025-07-01T01:51:38+00:00Pierre Gondoispierre.gondois@arm.com2025-04-30T10:57:01+00:00urn:sha1:f54fe78d9a1a760bdfd50131221cb93916ce5865
Running the vulture tool gave the following report.
Remove the unused import.
- BPDG/BPDG.py:21:
unused import 'encodings' (90% confidence)
- build/build.py:61:
unused import 'Manager' (90% confidence)
- Ecc/CParser4/CLexer.py:4:
unused import 'TextIO' (90% confidence)
- Ecc/CParser4/CParser.py:5:
unused import 'TextIO' (90% confidence)
- Eot/CParser4/CLexer.py:4:
unused import 'TextIO' (90% confidence)
- Eot/CParser4/CParser.py:5:
unused import 'TextIO' (90% confidence)
- Eot/EotMain.py:28:
unused import 'ConvertGuid' (90% confidence)
- GenFds/FdfParser.py:16:
unused import 'hexdigits' (90% confidence)
- Table/TableEotReport.py:16:
unused import 'EotToolError' (90% confidence)
- UPT/Library/CommentGenerating.py:19:
unused import 'USAGE_ITEM_NOTIFY' (90% confidence)
- UPT/Library/ParserValidate.py:18:
unused import 'COMPONENT_TYPE_LIST' (90% confidence)
- UPT/Library/UniClassObject.py:25:
unused import 'CheckUTF16FileHeader' (90% confidence)
Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>