OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/boards/Kconfig

31 lines
670 B
Plaintext
Raw Normal View History

kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
build: add Kconfig mechanism for deprecating boards If a deprecated board is built, a warning is presented indicating what future release the board will be removed. Change-Id: Ib166198d8b71303b990a30f79429f51871591a97 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 04:05:35 +08:00
config BOARD_DEPRECATED
string
help
kconfig: fix help syntax and add spaces Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-13 23:08:21 +08:00
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.
build: add Kconfig mechanism for deprecating boards If a deprecated board is built, a warning is presented indicating what future release the board will be removed. Change-Id: Ib166198d8b71303b990a30f79429f51871591a97 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-10-20 04:05:35 +08:00
boards: mark qemu targets with a unified Kconfig This will allow checking if we are building for QEMU globally, without having to know the exact architecture and board name. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-07-26 20:08:21 +08:00
config QEMU_TARGET
boards: Fix QEMU_TARGET config prompt and default The default boolean setting for QEMU_TARGET was incorrectly placed in the prompt field, so it was showing up as a config option in 'make menuconfig' when it should be hidden. Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-08-01 04:38:03 +08:00
bool
boards: mark qemu targets with a unified Kconfig This will allow checking if we are building for QEMU globally, without having to know the exact architecture and board name. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-07-26 20:08:21 +08:00
help
Mark all QEMU targets with this variable for checking whether we are
running in an emulated environment.
kconfig: Get rid of 'option env' bounce symbols This commit gets rid of the 'option env="ENV_VAR"' bounce symbols. "$FOO" now expands directly to the value of the environment variable FOO, instead of to the value of the Kconfig symbol FOO. This change is likely to soon appear in the C tools as well. Those 'option env' symbols always seemed kinda pointless, and have broken dependency handling due to forcing symbol evaluation during parsing, before all the symbols have even been seen. Compatibility with the C tools could be retained by naming all 'option env' symbols the same as the environment variable they reference. This commit also updated the Zephyr documentation to explain the new behavior. It's relevant for $ZEPHYR_BASE and out-of-tree Kconfig extensions. Commit message from Kconfiglib (cbf32e29a130d) ============================================== Make "$FOO" directly reference the environment variable $FOO in e.g. 'source' statements, instead of the symbol FOO. Use os.path.expandvars() to expand strings (which preserves "$FOO" as-is if no environment variable FOO exists). This gets rid of the 'option env' "bounce" symbols, which are mostly just spam and are buggy in the C tools (dependencies aren't always respected, due to parsing and evaluation getting mixed up). The same change will probably appear soon in the C tools as well. Keep accepting 'option env' to preserve some backwards compatibility, but ignore it when expanding strings. For compatibility with the C tools, bounce symbols will need to be named the same as the environment variables they reference (which is the case for the Linux kernel). This is a compatibility break, so the major version will be bumped to 6 at the next release. The main motivation for adding this now is to allow recording properties on each MenuNode in a clean way. 'option env' symbols interact badly with delayed dependency propagation. Side note: I have a feeling that recording environment variable values might be redundant to trigger rebuilds if sync_deps() is run at each compile. It should detect all changes to symbol values due to environment variables changing value. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-05-17 02:24:03 +08:00
# $ENV_VAR_BOARD_DIR might be a glob pattern
kconfig: Make 'source' non-globbing and use 'gsource' Until now, Zephyr has used a patched Kconfiglib that turns 'source' into a globbing source (by replacing 'source' with 'gsource' at the token level). There's two problems with this: - The patch needs to be maintained separately - Misspelled filenames are silently ignored, as they look like glob patterns that don't match anything Fix it as follows: 1. Replace all 'source' statements that use wildcards with 'gsource' 2. Remove the custom Kconfiglib patch so that 'source' no longer globs The sed pattern '/source.*[*?]/s/source/gsource/' was run over all Kconfig* files to do the replacement. source's that use environment variables that might contain glob patterns were manually changed to gsource. Building the docs in doc/ is a good test, as doc/Makefile deliberately sets the environment variables to glob up as many Kconfig files as possible. Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
2018-05-08 15:31:48 +08:00
kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
choice
prompt "Board Selection"
kconfig: Get rid of 'option env' bounce symbols This commit gets rid of the 'option env="ENV_VAR"' bounce symbols. "$FOO" now expands directly to the value of the environment variable FOO, instead of to the value of the Kconfig symbol FOO. This change is likely to soon appear in the C tools as well. Those 'option env' symbols always seemed kinda pointless, and have broken dependency handling due to forcing symbol evaluation during parsing, before all the symbols have even been seen. Compatibility with the C tools could be retained by naming all 'option env' symbols the same as the environment variable they reference. This commit also updated the Zephyr documentation to explain the new behavior. It's relevant for $ZEPHYR_BASE and out-of-tree Kconfig extensions. Commit message from Kconfiglib (cbf32e29a130d) ============================================== Make "$FOO" directly reference the environment variable $FOO in e.g. 'source' statements, instead of the symbol FOO. Use os.path.expandvars() to expand strings (which preserves "$FOO" as-is if no environment variable FOO exists). This gets rid of the 'option env' "bounce" symbols, which are mostly just spam and are buggy in the C tools (dependencies aren't always respected, due to parsing and evaluation getting mixed up). The same change will probably appear soon in the C tools as well. Keep accepting 'option env' to preserve some backwards compatibility, but ignore it when expanding strings. For compatibility with the C tools, bounce symbols will need to be named the same as the environment variables they reference (which is the case for the Linux kernel). This is a compatibility break, so the major version will be bumped to 6 at the next release. The main motivation for adding this now is to allow recording properties on each MenuNode in a clean way. 'option env' symbols interact badly with delayed dependency propagation. Side note: I have a feeling that recording environment variable values might be redundant to trigger rebuilds if sync_deps() is run at each compile. It should detect all changes to symbol values due to environment variables changing value. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-05-17 02:24:03 +08:00
gsource "$ENV_VAR_BOARD_DIR/Kconfig.board"
kconfig: add board configurations First step for adding the new board layer. Create configurations for the various boards we support on x86 under boards with the new Kconfig variables defining them. The board selection is optional, that means you will be able to run make menuconfig and create your own .config and select any SoC. Change-Id: If08e88e9675d13f0f0501ef6750b9424b15f5dc8 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-13 18:54:28 +08:00
endchoice
boards: add a menu surrounding board Kconfig This adds a menu to enclose all board Kconfig. So the board configs do not appear on the top level out of context in menuconfig. This also reflects the SoC options where these are under menus for each architecture. Change-Id: I76ce2bf1acf7cbd2673ceb2eac71e96cdca2ff35 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-16 01:27:39 +08:00
menu "Board Options"
kconfig: Get rid of 'option env' bounce symbols This commit gets rid of the 'option env="ENV_VAR"' bounce symbols. "$FOO" now expands directly to the value of the environment variable FOO, instead of to the value of the Kconfig symbol FOO. This change is likely to soon appear in the C tools as well. Those 'option env' symbols always seemed kinda pointless, and have broken dependency handling due to forcing symbol evaluation during parsing, before all the symbols have even been seen. Compatibility with the C tools could be retained by naming all 'option env' symbols the same as the environment variable they reference. This commit also updated the Zephyr documentation to explain the new behavior. It's relevant for $ZEPHYR_BASE and out-of-tree Kconfig extensions. Commit message from Kconfiglib (cbf32e29a130d) ============================================== Make "$FOO" directly reference the environment variable $FOO in e.g. 'source' statements, instead of the symbol FOO. Use os.path.expandvars() to expand strings (which preserves "$FOO" as-is if no environment variable FOO exists). This gets rid of the 'option env' "bounce" symbols, which are mostly just spam and are buggy in the C tools (dependencies aren't always respected, due to parsing and evaluation getting mixed up). The same change will probably appear soon in the C tools as well. Keep accepting 'option env' to preserve some backwards compatibility, but ignore it when expanding strings. For compatibility with the C tools, bounce symbols will need to be named the same as the environment variables they reference (which is the case for the Linux kernel). This is a compatibility break, so the major version will be bumped to 6 at the next release. The main motivation for adding this now is to allow recording properties on each MenuNode in a clean way. 'option env' symbols interact badly with delayed dependency propagation. Side note: I have a feeling that recording environment variable values might be redundant to trigger rebuilds if sync_deps() is run at each compile. It should detect all changes to symbol values due to environment variables changing value. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-05-17 02:24:03 +08:00
gsource "$ENV_VAR_BOARD_DIR/Kconfig"
boards: add a menu surrounding board Kconfig This adds a menu to enclose all board Kconfig. So the board configs do not appear on the top level out of context in menuconfig. This also reflects the SoC options where these are under menus for each architecture. Change-Id: I76ce2bf1acf7cbd2673ceb2eac71e96cdca2ff35 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-16 01:27:39 +08:00
endmenu
boards/shields: Add connector flags for compatibility checks In order to provide a way to control boards/shields compatibility, provide connector flags. One should select this flag in Kconfig.board to state connector compatibility for the board. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2018-04-24 23:17:51 +08:00
menu "Shields"
source "boards/shields/Kconfig"
endmenu