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

21 lines
385 B
Plaintext
Raw Normal View History

ext: libmetal: Change build integration so its not recursive With recent changes to libmetal we can now include and build it directly as a zephyr library rather than doing a recursive make. We remove ext/hal/libmetal.cmake as part of this change and introduce a Kconfig option for libmetal. This is a partial fix for issue #7673. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-05-22 23:52:12 +08:00
#
# Copyright (c) 2018 Linaro Limited
#
# SPDX-License-Identifier: Apache-2.0
#
kconfig: libmetal: Have LIBMETAL_SRC_PATH depend on LIBMETAL Kconfig options are often either of the type 'feature' or 'configuration'. Meaning, either an option controls whether a feature is enabled, or it adjusts/configures an already enabled feature. Configuration of features should depend on the feature they are configuring or else noise is created both in the Kconfig output and in the Kconfig menu. In this commit we add a dependency from a configuration option to it's feature option. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-12-27 22:33:00 +08:00
menuconfig LIBMETAL
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
bool "libmetal Support"
ext: libmetal: Change build integration so its not recursive With recent changes to libmetal we can now include and build it directly as a zephyr library rather than doing a recursive make. We remove ext/hal/libmetal.cmake as part of this change and introduce a Kconfig option for libmetal. This is a partial fix for issue #7673. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-05-22 23:52:12 +08:00
help
This option enables the libmetal HAL abstraction layer
ext: hal: libmetal: Allow for libmetal source to be external Introduce a Kconfig option (CONFIG_LIBMETAL_SRC_PATH) that allows us to point to an external copy of libmetal. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-05-24 23:30:38 +08:00
kconfig: libmetal: Have LIBMETAL_SRC_PATH depend on LIBMETAL Kconfig options are often either of the type 'feature' or 'configuration'. Meaning, either an option controls whether a feature is enabled, or it adjusts/configures an already enabled feature. Configuration of features should depend on the feature they are configuring or else noise is created both in the Kconfig output and in the Kconfig menu. In this commit we add a dependency from a configuration option to it's feature option. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-12-27 22:33:00 +08:00
if LIBMETAL
ext: hal: libmetal: Allow for libmetal source to be external Introduce a Kconfig option (CONFIG_LIBMETAL_SRC_PATH) that allows us to point to an external copy of libmetal. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-05-24 23:30:38 +08:00
config LIBMETAL_SRC_PATH
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
string "libmetal library source path"
ext: hal: libmetal: Allow for libmetal source to be external Introduce a Kconfig option (CONFIG_LIBMETAL_SRC_PATH) that allows us to point to an external copy of libmetal. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-05-24 23:30:38 +08:00
default "libmetal"
help
This option specifies the path to the source for the libmetal library
kconfig: libmetal: Have LIBMETAL_SRC_PATH depend on LIBMETAL Kconfig options are often either of the type 'feature' or 'configuration'. Meaning, either an option controls whether a feature is enabled, or it adjusts/configures an already enabled feature. Configuration of features should depend on the feature they are configuring or else noise is created both in the Kconfig output and in the Kconfig menu. In this commit we add a dependency from a configuration option to it's feature option. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-12-27 22:33:00 +08:00
endif # LIBMETAL