Lines Matching full:build
1 Build Options
4 The TF-A build system supports the following build options. Unless mentioned
5 otherwise, these options are expected to be specified at the build command
7 build system doesn't track dependency for build options. Therefore, if any of
8 the build options are changed from a previous build, a clean build must be
13 Common build options
29 - ``ARCH`` : Choose the target build architecture for TF-A. It can take either
33 - ``ARM_ARCH_FEATURE``: Optional Arm Architecture build option which specifies
48 - ``BL2``: This is an optional build option which specifies the path to BL2
52 - ``BL2U``: This is an optional build option which specifies the path to
55 - ``BL2_AT_EL3``: This is an optional build option that enables the use of
67 - ``BL31``: This is an optional build option which specifies the path to
75 - ``BL32``: This is an optional build option which specifies the path to
79 - ``BL32_EXTRA1``: This is an optional build option which specifies the path to
82 - ``BL32_EXTRA2``: This is an optional build option which specifies the path to
128 compilation of each build. It must be set to a C string (including quotes
133 build to be uniquely identified. Defaults to the current git commit id.
135 - ``BUILD_BASE``: Output directory for the build. Defaults to ``./build``
138 addition to the options set by the build system.
155 this is only enabled for a debug build of the firmware.
197 - ``DEBUG``: Chooses between a debug and release build. It can take either 0
200 - ``DECRYPTION_SUPPORT``: This build flag enables the user to select the
256 in the build command line.
394 instrumented. Enabling this option enables the ``ENABLE_PMF`` build option
402 and TF-A support is experimental. At this time, this build option cannot be
404 build with these options will fail. Default is 0.
423 which are aliased by the SIMD and FP registers. The build option is not
424 compatible with the ``CTX_INCLUDE_FPREGS`` build option, and will raise an
427 since SME encompasses SVE. At this time, this build option cannot be used on
444 flag depends on ``DECRYPTION_SUPPORT`` build flag.
447 This flag depends on ``DECRYPTION_SUPPORT`` build flag.
451 on ``DECRYPTION_SUPPORT`` build flag.
455 build flag.
472 injection from lower ELs, and this build option enables lower ELs to use
481 through feature specific build flags are supported by the PE or not by
487 and restore routines guarded by these build flags. Henceforth validating them
490 The mechanism permits the build flags to take values 0, 1 or 2 and
493 Lets consider ``ENABLE_FEAT_HCX``, build flag for ``FEAT_HCX`` as an example:
501 In the above example, if the feature build flag, ``ENABLE_FEAT_HCX`` set to
513 mechanism, by enabling it to validate whether they have set their build flags
516 - ``FIP_NAME``: This is an optional build option which specifies the FIP
519 - ``FWU_FIP_NAME``: This is an optional build option which specifies the FWU
531 This flag depends on ``DECRYPTION_SUPPORT`` build flag.
533 - ``GENERATE_COT``: Boolean flag used to build and execute the ``cert_create``
535 :ref:`Trusted Board Boot`. The build system then calls ``fiptool`` to
553 inherent support for specific EL3 type interrupts. Setting this build option
574 build and run-time optimizations during boot and power management operations.
591 bottom, higher addresses at the top. This build flag can be set to '1' to
595 - ``JUNO_AARCH32_EL3_RUNTIME``: This build flag enables you to execute EL3
601 - ``KEY_ALG``: This build flag enables the user to select the algorithm to be
608 - ``KEY_SIZE``: This build flag enables the user to select the key size for
623 - ``HASH_ALG``: This build flag enables the user to select the secure hash
628 addition to the one set by the build system.
631 output compiled into the build. This should be one of the following:
643 the build. The default value is 40 in debug builds and 20 in release builds.
667 is required in order to build the ``fwu_fip`` target.
684 - ``PLAT``: Choose a platform to build TF-A for. The chosen platform name
686 platform makefile named ``platform.mk``. For example, to build TF-A for the
758 is required in order to build the ``fwu_fip`` target.
763 When set to ``1``, the build option ``EL3_EXCEPTION_HANDLING`` must also be
792 This build option is only valid if ``ARCH=aarch64``. The value should be
826 description of secure partitions. The build system will parse this file and
871 WFE instruction. ``ENABLE_FEAT_TWED`` build option must be enabled to set
877 linker. When the ``LINKER`` build variable points to the armlink linker,
907 SDEI_SUPPORT build flag is enabled.
920 - ``V``: Verbose build. If assigned anything other than 0, the build commands
924 Defaults to a string formed by concatenating the version number, build type
925 and build string.
967 This option is enabled by build only if platform sets any of above defines
978 path on the host machine which is used to build certificate generation and
1050 To compile a debug version and make the build more verbose use
1070 Extra debug options can be passed to the build system by setting ``CFLAGS`` or
1083 ``SPIN_ON_BL1_EXIT=1`` build flag. Refer to the :ref:`build_options_common`