Lines Matching full:build

29 	bool "Build with TF-M as the Secure Execution Environment"
37 	  When enabled, this option instructs the Zephyr build process to
44 	  them, are generated during the normal Zephyr build process.
80 	  Build profile used to build tfm_s image. The available values are
85 	prompt "TF-M build profile"
89 	  The TF-M build profile selection. Can be empty (not set),
95 	bool "TF-M build profile is not set"
98 	bool "TF-M build profile: small"
101 	bool "TF-M build profile: medium"
104 	bool "TF-M build profile: large"
109 	prompt "The build type for TFM"
116 	bool "Release build"
119 	bool "Release build with Debug info"
122 	bool "Release build, optimized for size"
125 	bool "Debug build"
138 	  1,2 or 3; the default is set by build configuration. When TF-M
208 	  This config adds MCUboot to the build - built via TFM's build system.
211 	bool "Build the TF-M Non-Secure application and libraries"
213 	  Instruct the TF-M build system to build the TF-M Non-Secure
217 	  easiest way to build the TF-M regression tests application and test
218 	  support libraries in the zephyr build system.
224 	  The TF-M build system can produce multiple executable files.
234 	  zephyr build system.
239 	  The TF-M build system produces an interface source file for accessing
243 	  Note: This is an auto-generated configuration in the TF-M build
244 	  system. When this option is not enabled in the TF-M build system this
266 	   case MCUboot will be fetched by the TF-M build during
267 	   build time. The default option ensures that Zephyr builds
277 	bool "TF-M to automatically download MCUboot during build"
279 	  TF-M builds with BL2 will let the TF-M build to automatically
280 	  fetch and check-out the MCUboot version to use in the build.
293 	  TF-M build system to automatically download this.
341 	  When enabled, this option signifies that the TF-M build includes
348 	  When enabled, this option signifies that the TF-M build includes