Searched full:build (Results 1876 – 1900 of 2206) sorted by relevance
1...<<71727374757677787980>>...89
237 #. Build the Zephyr kernel and the :zephyr:code-sample:`blinky` sample application.246 :goals: build254 :goals: build311 #. Build application including the snippet.
18 Build System34 * Build type by setting ``CONF_FILE`` to ``prj_<build>.conf`` is now deprecated, users should124 fail the build if the device does not exist.
226 Build and flash applications as usual (see :ref:`build_an_application` and277 ``-DBOARD_DEBUG_RUNNER=jlink`` when you invoke ``west build`` to override the284 :goals: build355 >>> load build/zephyr/zephyr.bin
40 For example, the following will build this project with userspace support:42 EXTRA_CONF_FILE="prj.userspace.conf" west build -p -b <board> <path to project>165 for the default build. Not only does each stack frame in the call tree have222 times than for the default build when context switching is involved. A blanket358 the default build scenario. Enabling userspace results in additional
590 Build system:604 - doc/build/606 - scripts/build/616 - "area: Build System"863 - scripts/build/gen_symtab.py933 - doc/build/dts/936 - doc/build/kconfig/preprocessor-functions.rst2461 - doc/build/kconfig/2468 See https://docs.zephyrproject.org/latest/build/kconfig/index.html and4415 - doc/build/sysbuild/[all …]
9 # <build>/zephyr/include/generated/autoconf.h.113 # configure time or menuconfig and related build target.
377 .note.gnu.build-id : ALIGN(4)380 *(.note.gnu.build-id)
160 Then build and flash the application in the usual way.167 :goals: build flash
383 .note.gnu.build-id : ALIGN(4)386 *(.note.gnu.build-id)
15 /* Include autoconf for cases when this file is used in special build (e.g. TFM) */
11 completely. This script is the first step in the build system's process of
192 /* Count the number of active channels and build a map that translates in max30101_init()
191 logger.info("Skipping coverage report generation due to --build-only.")
221 * and holds the build-time configuration information for the fixed MMU
226 * and holds the build-time configuration information for the fixed MPU
136 * suggested that at build time drivers allocate space for the
67 Build and flash applications as usual (see :ref:`build_an_application` and
100 :goals: build flash
169 /* Compile-time assertion that makes the build to fail.
82 *** Booting Zephyr OS build zephyr-v3.3.0 ***
125 * region are configured at build-time, so no map is needed. in fill_multi_heap()
496 Build and flash511 Then build and flash the application in the usual way.516 :goals: build flash519 Please use reel_board@2 to build a application for the board equipped with525 :goals: build flash549 You can build and flash the examples to make sure Zephyr is running correctly on
336 found in :ref:`nordic_segger_flashing`. Then build and flash352 Then build and flash the application in the usual way.357 :goals: build flash377 You can build and flash the examples to make sure Zephyr is
377 Typically, users will need to add a configuration file overlay to the build,517 device stack. Follow the general build procedure to build the USB sample for524 west build -t run
347 found in :ref:`nordic_segger_flashing`. Then build and flash363 Then build and flash the application in the usual way.368 :goals: build flash388 You can build and flash the examples to make sure Zephyr is
