Lines Matching full:build

2 Build instructions
6     The build process was changed a lot in Q3 2023 and included into the release v2.0.
20     Refer to :doc:`Building Tests </building/tests_build_instruction>` on how to build TF-M
37     Build Tests <tests_build_instruction>
47 This build generates the SPE binary and artifacts, necessary for :ref:`Building NSPE`.
77 only mandatory argument to TF-M build is a platform name, provided via
81 - An absolute path of target platform, mainly used for out-of-tree platform build.
89 - Build directory ``<Build Dir>`` - the location of all intermediate files required to produce
90   a build target.
91 - Install directory ``<Artifact Dir>`` - the location of the build output files.
115 Build type
117 By default, a MinSizeRel configuration is built. Alternate build types can be
138 In a successful build, a set of files will be created in the ``<Artifact Dir>``.
139 By default, it is ``<Build Dir>\api_ns`` subfolder but you can redirect the
144 Other build parameters
153 | BL2                        | Build level 2 secure bootloader.         | ON            |
175     cmake -S <TF-M source dir> -B <Build Dir> -DTFM_PLATFORM=<platform>
176     cmake --build <Build Dir> -- install
179     It is recommended to clean up the build directory before re-build if the config
189     cmake -S . -B build -DTFM_PLATFORM=arm/mps2/an521
190     cmake --build build -- install
194   - build SPE in the ``build`` folder
198   - install output files in ``build/api_ns`` folder *by default*. You can specify
203     It is recommended to build each different build configuration in a separate
204     build directory.
206 CMake can generate code for many native build systems. TF-M is tested with
209 :ref:`Build type` using ArmClang :ref:`Toolchains` you can use the following:
214 …cmake -S . -B build -DTFM_PLATFORM=arm/mps2/an521 -GNinja -DTFM_TOOLCHAIN_FILE=toolchain_ARMCLANG.…
215     cmake --build build -- install
222 The TF-M build system will fetch all dependencies by default with appropriate
223 versions and store them inside the build tree. In this case, the build tree
227 downloaded every time the build directory is deleted, then the following
233 file which will be included in a build if it exists.
279    let TF-M download it once and then copy them out of the ``build/lib/ext`` folder.
281 Now build TF-M binaries
286 …cmake -S . -B build -DTFM_PLATFORM=arm/mps2/an521 -DMBEDCRYPTO_PATH=<Mbed Crypto base folder>/mbed…
287     cmake --build build -- install
344 Toolchain used to build NSPE can be different from what is used to build SPE.