It doesn't make sense to use the `-pedantic` flag when building the
Trusted Firmware as we use GNU extensions and so our code is not
fully ISO C compliant. This flag only makes sense if the code intends to
be ISO C compliant.
Change-Id: I6273564112759ff57f03b273f5349733a5f38aef
Signed-off-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>
# Process platform overrideable behaviour
################################################################################
-# Check if -pedantic option should be used
-ifeq (${DISABLE_PEDANTIC},0)
- TF_CFLAGS += -pedantic
-endif
-
# Using the ARM Trusted Firmware BL2 implies that a BL33 image also needs to be
# supplied for the FIP and Certificate generation tools. This flag can be
# overridden by the platform.
* `DEBUG`: Chooses between a debug and release build. It can take either 0
(release) or 1 (debug) as values. 0 is the default.
-* `DISABLE_PEDANTIC`: When set to 1 it will disable the -pedantic option in
- the GCC command line. Default is 0.
-
* `EL3_PAYLOAD_BASE`: This option enables booting an EL3 payload instead of
the normal boot flow. It must specify the entry point address of the EL3
payload. Please refer to the "Booting an EL3 payload" section for more
# Build platform
DEFAULT_PLAT := fvp
-# By default, use the -pedantic option in the gcc command line
-DISABLE_PEDANTIC := 0
-
# Flag to enable Performance Measurement Framework
ENABLE_PMF := 0