Lines Matching full:build

28 	bool "Build with TF-M as the Secure Execution Environment"
36 	  When enabled, this option instructs the Zephyr build process to
43 	  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: not set (base)"
98 	bool "TF-M build profile: small"
101 	bool "TF-M build profile: medium"
104 	bool "TF-M build profile: ARoT-less"
107 	bool "TF-M build profile: large"
112 	prompt "The build type for TFM"
119 	bool "Release build"
122 	bool "Release build with Debug info"
125 	bool "Release build, optimized for size"
128 	bool "Debug build"
141 	  1,2 or 3; the default is set by build configuration. When TF-M
230 	  This config adds MCUboot to the build - built via TFM's build system.
235 	  The TF-M build system can produce multiple executable files.
245 	  zephyr build system.
250 	  The TF-M build system produces an interface source file for accessing
254 	  Note: This is an auto-generated configuration in the TF-M build
255 	  system. When this option is not enabled in the TF-M build system this
277 	   case MCUboot will be fetched by the TF-M build during
278 	   build time. The default option ensures that Zephyr builds
288 	bool "TF-M to automatically download MCUboot during build"
290 	  TF-M builds with BL2 will let the TF-M build to automatically
291 	  fetch and check-out the MCUboot version to use in the build.
304 	  TF-M build system to automatically download this.
353 	  When enabled, this option signifies that the TF-M build includes
360 	  When enabled, this option signifies that the TF-M build includes