Lines Matching full:sysbuild

3 Sysbuild images
6 Sysbuild can be used to add additional images to builds, these can be added by projects or boards
18 Applications can add sysbuild images using the ``sysbuild.cmake`` file in the application
19 directory, the inclusion of images can be controlled with a ``Kconfig.sysbuild`` file in the
25 Boards can add sysbuild images by using the ``sysbuild.cmake`` file in the board directory, the
26 inclusion of images can be controlled with a ``Kconfig.sysbuild`` file in the board directory.
31 SoCs can add sysbuild images by using the ``sysbuild.cmake`` file in the soc directory.
36 :ref:`modules` can add sysbuild images with the ``sysbuild-cmake`` and ``sysbuild-kconfig``
62    .. group-tab:: ``Kconfig.sysbuild``
73          Remember to have ``source "share/sysbuild/Kconfig"`` in the file if this
74          is being applied in an application ``Kconfig.sysbuild`` file.
77    .. group-tab:: ``sysbuild.cmake``
99    :west-args: --sysbuild
113    .. group-tab:: ``Kconfig.sysbuild``
160          Remember to have ``source "${ZEPHYR_BASE}/share/sysbuild/Kconfig"`` in the file if this
161          is being applied in an application ``Kconfig.sysbuild`` file.
163    .. group-tab:: ``sysbuild.cmake``
185    :west-args: --sysbuild
193    .. group-tab:: ``Kconfig.sysbuild``
227    :west-args: --sysbuild
236 Sysbuild supports being able to set image configuration (Kconfig options) and also supports
238 option to be added to sysbuild itself and then to configure it globally or selectively.
246 Sysbuild can be used to set image configuration **before the CMake configuration of images takes
263 These can safely be used in an application, board or SoC ``sysbuild.cmake`` file, as that file is
265 :ref:`sysbuild using modules <sysbuild_module_integration>` the pre-CMake hook should be used
283 different images to correctly configure them based upon options set in sysbuild. MCUboot
285 which allows sysbuild to be the central location for things like the signing key which are then
289 application being configured, the ``set_config_*`` sysbuild CMake functions can be used to set
290 configuration and the sysbuild Kconfig can be read, for example:
302 must be done in a ``sysbuild.cmake`` file for an application. This can be used to add an image
307    .. group-tab:: ``sysbuild.cmake``
336 ``ExternalZephyrProject_Add()`` require changes to sysbuild code in Zephyr. This should only be
342 :zephyr_file:`share/sysbuild/cmake/modules/sysbuild_extensions.cmake` in the
344 sysbuild image, for example:
350       Full file path: ``share/sysbuild/cmake/modules/sysbuild_extensions.cmake``
375    .. group-tab:: ``sysbuild.cmake``
390       Full file path: ``share/sysbuild/image_configurations/MY_CUSTOM_TYPE_image_default.cmake``
403 Kconfig values from images can be read by sysbuild **after the CMake configuration of images has
404 taken place**. This can be used to check configuration or to adjust additional sysbuild tasks
412 :ref:`sysbuild is extended by a module <sysbuild_module_integration>` or inside of a ``sysbuild/CMa…
432    .. group-tab:: ``sysbuild/CMakeLists.txt``
436          find_package(Sysbuild REQUIRED HINTS $ENV{ZEPHYR_BASE})
438          project(sysbuild LANGUAGES)