Searched refs:builds (Results 126 – 150 of 191) sorted by relevance
12345678
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 17 or other types of builds you want to run.
93 Here is an example. For details, see :ref:`west-multi-domain-builds` in
113 Since sysbuild supports both single- and multi-image builds, this lets you
355 This builds ``hello_world`` and ``mcuboot`` for the ``reel_board``, and then
|
| D | images.rst | 6 Sysbuild can be used to add additional images to builds, these can be added by projects or boards
|
| /Zephyr-latest/doc/services/retention/ |
| D | index.rst | 15 The retention system builds on top of the retained data driver, and adds
|
| /Zephyr-latest/samples/bluetooth/hci_uart/ |
| D | README.rst | 21 By default the controller builds use the following settings:
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/os_mgmt/ |
| D | Kconfig | 192 Note: This will invalidate reproducible builds of the firmware as it will embed the
|
| /Zephyr-latest/subsys/bluetooth/common/ |
| D | Kconfig | 195 # Host-only builds.
198 # for Host only builds, or when Controller-to-Host ACL data flow control
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 161 builds. To change the Zephyr package, for example to test the application using Zephyr base
252 This can be useful to avoid accidental builds when only part of a workspace has been
|
| /Zephyr-latest/cmake/ |
| D | mcuboot.cmake | 7 # It builds signed binaries using imgtool as a post-processing step
|
| /Zephyr-latest/tests/drivers/build_all/gpio/ |
| D | app.overlay | 6 * Application overlay for testing driver builds
|
| /Zephyr-latest/doc/services/ |
| D | formatted_output.rst | 80 method scans format string and based on detected format specifiers builds the
|
| /Zephyr-latest/cmake/modules/ |
| D | kernel.cmake | 105 In-source builds are not supported.\
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 25 There are a few reasons why twister only builds a test and doesn't run it:
369 are only run under certain circumstances, like daily builds. These test
429 actually builds. A ``build_only`` test is not designed to be run in any
431 that the code builds.
434 enabled in Zephyr and that the code builds, for example sensor drivers. Such
1083 the scope of builds and tests if applicable to platforms defined under the
|
| D | ztest.rst | 583 your project's :file:`CMakeLists.txt` to let Zephyr find your header file during builds.
602 tests. For native simulator builds you can provide the seed as an argument to
|
| D | pytest.rst | 65 provided in the ``testcase.yaml`` file, Twister builds the application from ``src`` and then, if the
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 569 following code builds on the examples above and publishes to channel ``acc_chan``. The code is
611 For example, the following code builds on the examples above and forces a notification for the
630 channel or observer on the same call. The following code builds on the examples above and displays
811 The following code builds on the examples above and claims the ``acc_chan`` to set the ``user_data``
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.10.rst | 214 * :github:`1332` - sanitycheck builds too many duplicates in CI, make it smarter
321 * :github:`3682` - incremental builds do not work properly in Windows
503 * :github:`5008` - system call headers are not properly regenerated in CMake on incremental builds
|
| /Zephyr-latest/include/zephyr/arch/x86/ia32/ |
| D | linker.ld | 23 * For builds using XIP, there is a different load memory address (LMA) and
|
| /Zephyr-latest/boards/st/stm32h747i_disco/doc/ |
| D | index.rst | 163 See :ref:`build_an_application` for more information about application builds.
|
| /Zephyr-latest/doc/ |
| D | glossary.rst | 155 introducing both secure and non-secure builds for platforms with Trusted
|
| /Zephyr-latest/boards/nxp/frdm_mcxn947/doc/ |
| D | index.rst | 323 For dual core builds, the secondary core should be placed into a loop,
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 33 - CI sees the tag, builds and runs tests; Test teams analyse the report from the
212 automated builds and CI tools.
|
| /Zephyr-latest/soc/espressif/esp32/ |
| D | default_appcpu.ld | 130 /* Vectors according to builds/RF-2015.2-win32/esp108_v1_2_s5_512int_2/config.html */
|
| /Zephyr-latest/arch/arm/core/ |
| D | Kconfig | 83 Thumb-2 technology builds on the success of Thumb, the innovative
|
| /Zephyr-latest/ |
| D | Kconfig.zephyr | 693 control over this can be useful for reproducible builds
716 from the build process. Note this breaks incremental builds, west spdx
967 failure logs more deterministic and most importantly makes builds more
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | board_porting.rst | 791 board ``plank`` defines revisions ``0.5.0``, and ``1.5.0`` and the user builds
804 and the user builds for ``plank@E``, the build system will target revision ``D``
823 When the user builds for board ``plank@<revision>`` it is possible to make
|
12345678
