audk/BaseTools/Conf
Ard Biesheuvel c25d390552 BaseTools/tools_def IA32: disable PIE code generation explicitly
As a security measure, some distros now build their GCC toolchains with
PIE code generation enabled by default, because it is a prerequisite
for ASLR to be enabled when running the executable.

This typically results in slightly larger code, but it also generates
ELF relocations that our tooling cannot deal with, so let's disable it
explicitly when using GCC49 or later for IA32. (Note that this does not
apply to X64: it uses PIE code deliberately in some cases, and our
tooling does deal with the resuling relocations)

Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
2018-06-12 08:08:49 +02:00
..
XMLSchema BaseTools/Conf/XMLSchema: Reformat XML using Visual Studio 2013 2016-02-19 09:44:32 +08:00
Empty_Package_Information_Data_File.ini Sync BaseTools Branch (version r2271) to EDKII main trunk. 2011-08-26 07:46:26 +00:00
FrameworkDatabase.template Sync EDKII BaseTools to BaseTools project r1971 2010-05-18 05:04:32 +00:00
ReadMe.txt Restoring $WORKSPACE/BaseTools location, as the plan is to deprecate 2007-10-17 01:54:36 +00:00
build_rule.template BaseTools/Conf: Add VS2017/ARM64 support 2018-03-19 17:05:45 +08:00
target.template BaseTools: not specified value of MAX_CONCURRENT_THREAD_NUMBER 2018-02-09 08:33:46 +08:00
tools_def.template BaseTools/tools_def IA32: disable PIE code generation explicitly 2018-06-12 08:08:49 +02:00

ReadMe.txt

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This directory contains the template files for the next generation of the
EDK II Build infrastructure.  These files will be copied into the WORKSPACE's
Conf directory if and only if the target files do not exist.

These files may be updated frequently.

The XMLSchema directory contains the EDK II Packaging XML definitions.  The
schema may change in the future.  It differs somewhat from the early versions
of the XML Schema.