michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/share/sysbuild/Kconfig

79 lines
1.9 KiB
Text
Raw Permalink Normal View History

infrastructure: Remove hwmv1 support Removes support for the deprecated hardware model version 1 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-11-14 08:48:17 +00:00
# Copyright (c) 2021-2023 Nordic Semiconductor
cmake: initial sysbuild / multi image support This is the initial commit with system build, sysbuild. Using CMake as infrastructure together with the Zephyr sysbuild allows us to support a convenient way of building a sample and allow for extra images to be built as part of a larger system. It uses Kconfig for configuration of image builds. This allows for future extension with additional build images. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-06-22 11:05:49 +02:00
#
# SPDX-License-Identifier: Apache-2.0
infrastructure: Remove hwmv1 support Removes support for the deprecated hardware model version 1 Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-11-14 08:48:17 +00:00
config BOARD
string
default "$(BOARD)"
help
This option holds the name of the board and is used to locate the files
related to the board in the source tree (under boards/).
The Board is the first location where we search for a linker.ld file,
if not found we look for the linker file in
soc/<arch>/<family>/<series>
config BOARD_REVISION
def_string "$(BOARD_REVISION)"
help
If the BOARD has a revision field set, this is the revision.
Otherwise, it is the empty string. For example, if BOARD is
"plank@foo", this option will be "foo". If BOARD is "plank",
this option will be the empty string.
config BOARD_DEPRECATED_RELEASE
string
help
This hidden option is set in the board configuration and indicates
the Zephyr release that the board configuration will be removed.
When set, any build for that board will generate a clearly visible
deprecation warning.
source "boards/Kconfig.v2"
source "soc/Kconfig.v2"
sysbuild: include HWMv2 Kconfig in sysbuild Including HWMv2 Kconfig in sysbuild allows sysbuild to introduce configuration options or defaults based on selected board and SoC. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2023-11-03 13:47:54 +01:00
cmake: initial sysbuild / multi image support This is the initial commit with system build, sysbuild. Using CMake as infrastructure together with the Zephyr sysbuild allows us to support a convenient way of building a sample and allow for extra images to be built as part of a larger system. It uses Kconfig for configuration of image builds. This allows for future extension with additional build images. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-06-22 11:05:49 +02:00
comment "Sysbuild image configuration"
cmake: scripts: support board extension Fixes: #69548 Support extending an existing board with new board variants. This commit introduces the following changes to allow a board to be extended out-of-tree. The board yaml schema is extended to support an extend field which will be used to identify the board to be extended. A board 'plank' can be extended like this: > board: > extend: plank > variants: > - name: ext > qualifier: soc1 For the rest of the build system this means that there is no longer a single board directory. The existing CMake variable BOARD_DIR is kept and reference the directory which defines the board. A new CMake variable BOARD_DIRECTORIES provides a list of all directories which defines board targets for the board. This means the directory which defines the board as well as all directories that extends the board. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2024-05-08 13:10:48 +02:00
osource "$(KCONFIG_BOARD_DIR)/Kconfig.sysbuild"
sysbuild: add SoC-specific sysbuild configuration Sysbuild now supports SoC configuration, in addition to application and board. Signed-off-by: Marcin Szymczyk <marcin.szymczyk@nordicsemi.no>
2024-04-10 12:30:24 +02:00
osource "$(KCONFIG_BINARY_DIR)/soc/Kconfig.sysbuild"
cmake: initial sysbuild / multi image support This is the initial commit with system build, sysbuild. Using CMake as infrastructure together with the Zephyr sysbuild allows us to support a convenient way of building a sample and allow for extra images to be built as part of a larger system. It uses Kconfig for configuration of image builds. This allows for future extension with additional build images. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-06-22 11:05:49 +02:00
sysbuild: support Zephyr modules This commit extends the Zephyr module yaml scheme with additional entries for sysbuild in the build section. This allows for Zephyr modules to extend the sysbuild infrastructure by providing additional CMake and Kconfig files to be included in sysbuild. The new settings are: build: sysbuild-cmake: <path> sysbuild-kconfig: <path>/<file> sysbuild-ext: <true>|<false> sysbuild-kconfig-ext: <true>|<false> those settings follow the same pattern as the equivalent Zephyr build settings but are processed by sysbuild. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no> Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2023-02-20 10:00:38 +00:00
menu "Modules"
source "modules/Kconfig.sysbuild"
endmenu
cmake: initial sysbuild / multi image support This is the initial commit with system build, sysbuild. Using CMake as infrastructure together with the Zephyr sysbuild allows us to support a convenient way of building a sample and allow for extra images to be built as part of a larger system. It uses Kconfig for configuration of image builds. This allows for future extension with additional build images. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-06-22 11:05:49 +02:00
config EXPERIMENTAL
bool
help
Symbol that must be selected by a feature if it is considered to be
at an experimental implementation stage.
config WARN_EXPERIMENTAL
bool
prompt "Warn on experimental usage"
help
Print a warning when the Kconfig tree is parsed if any experimental
features are enabled.
config DEPRECATED
bool
help
Symbol that must be selected by a feature or module if it is
considered to be deprecated.
config WARN_DEPRECATED
bool
default y
prompt "Warn on deprecated usage"
help
Print a warning when the Kconfig tree is parsed if any deprecated
features are enabled.
cmake: support MCUBoot bootloader natively with SYSBuild This commit adds CMake and Kconfig files needed to build MCUboot as an extra image using SYSBuild. Building an application with MCUBoot using SYSBuild allows users to build both images using a single build. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2022-06-22 11:19:05 +02:00
sysbuild: Make the image processing order well-defined Adjust the order in which image-specific `sysbuild.cmake` files are iteratively included by sysbuild. This is motivated by the introduction of `sysbuild_add_dependencies()`. In the following example: sysbuild_add_dependencies(CONFIGURE my_sample sample_a sample_b) the `my_sample` image is expected to be added before this function is called. Success depends not only on the placement of the call, but on the order in which new images are added, which itself is influenced by the order in which `sysbuild.cmake` files are included. This last order can be tweaked to make the "dependencies" feature more user-friendly. This is done by rewriting the internal `sysbuild.cmake` processing loop into a new, general purpose function - `sysbuild_add_subdirectory()` - which is a wrapper for `add_subdirectory(<source_dir>)` that recursively includes `sysbuild.cmake` files for all images found in `<source_dir>`. With the new function, all images that are expected to be found in a given `<source_dir>` are guaranteed to be added around the same time. This wasn't the case with the old processing loop, because the image- specific `sysbuild.cmake` files (where "sub-images" could be defined) were left to be processed at the very end. Below is the initial order in which sysbuild will add all images. Note: the order of Zephyr modules (from 1 to n) is well-defined. 1. Main application (aka DEFAULT_IMAGE) 2. MCUboot (optional) 3. All images added via these directories: 3.1. <module-1>.sysbuild-cmake 3.2. <module-2>.sysbuild-cmake ... 3.n. <module-n>.sysbuild-cmake 4. All images added via these files: 4.1. ${BOARD_DIR}/sysbuild.cmake 4.2. ${APP_DIR}/sysbuild.cmake (aka sub-images of DEFAULT_IMAGE) These images are intended to be sorted for the users' convenience, from most to least important in the build system, or least to most dependent on other images for configuration (potentially). Finally, the use of `sysbuild_add_subdirectory()` requires updating the directory structure in sysbuild: ./images - All images should belong here. The `DEFAULT_IMAGE` should be the first and only image at the top level, so that it gets added first and its sub-images get added last. ./images/bootloader - Moved from ./bootloader. ./images/boards - Adds images from the board-specific `sysbuild.cmake` file. Signed-off-by: Grzegorz Swiderski <grzegorz.swiderski@nordicsemi.no>
2023-08-25 12:45:14 +02:00
rsource "images/Kconfig"
sysbuild: Add support for COMPILER_WARNINGS_AS_ERRORS Adds support for the Kconfig option to enable compiler warnings being treated as errors in all images that are build. This is a sticky-set option which means enabling it in sysbuild will enable it in all images, if it is then disabled in sysbuild it will not be disabled in any of the images as a result and would need to be manually unselected. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
2024-03-14 10:37:01 +00:00
menu "Build options"
rsource "build/Kconfig"
endmenu
Copy permalink