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

22 lines
761 B
CMake
Raw Normal View History

modules: introducing MODULE_EXT_ROOT to allow glue code in Zephyr repo This commit introduces MODULE_EXT_ROOT which allows CMake and Kconfig glue code to be placed outside of the Zephyr module repository. This allows for placing glue code in Zephyr, but also allows users to specify custom MODULE_EXT_ROOTs for glue code using either `-DMODULE_EXT_ROOT` or `zephyr/module.yml` with `build:settings:module_ext_root` settings. MODULE_EXT_ROOT' is a list of directories, similar to other roots such as BOARD_ROOT, DTS_ROOT, etc. The Zephyr repo folder ${ZEPHYR_BASE} is always to the MODULE_EXT_ROOT list as lowest priority. For each MODULE_EXT_ROOT, the file `<module_ext_root>/modules/modules.cmake` will be processed. In Zephyr repo, the folder `modules/<module>/` contains CMakeLists.txt and Kconfig glue code for the Zephyr module. A Zephyr module can specify that CMakeLists.txt and Kconfig glue code is placed in an external module root by specifying: ``` build: cmake-ext: True kconfig-ext: True ``` It is still possible to place the CMakeLists.txt and Kconfig files directly in the Zephyr module using the existing: ``` build: cmake: <path> kconfig: <file> ```. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-12-17 18:27:42 +08:00
# SPDX-License-Identifier: Apache-2.0
file(GLOB cmake_modules "${CMAKE_CURRENT_LIST_DIR}/*/CMakeLists.txt")
foreach(module ${cmake_modules})
get_filename_component(module_dir ${module} DIRECTORY)
get_filename_component(module_name ${module_dir} NAME)
cmake: zephyr modules: sanitize all module name when used as variable The introduction of Zephyr module glue code in the Zephyr repository introduces a Kconfig variable in the form of: `config ZEPHYR_<MODULE_NAME>_MODULE`. All Kconfig variables go into `autoconf.h`, therefore it is necessary to sanitize the Kconfig variable, so that it does not contain special characters. To ensure consistent variable name, then the module name will be sanitized in all variable use in both Kconfig and CMake. The sanitization is done be replacing all special characters with an underscore, `_`. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-01-19 19:01:38 +08:00
zephyr_string(SANITIZE TOUPPER MODULE_NAME_UPPER ${module_name})
modules: introducing MODULE_EXT_ROOT to allow glue code in Zephyr repo This commit introduces MODULE_EXT_ROOT which allows CMake and Kconfig glue code to be placed outside of the Zephyr module repository. This allows for placing glue code in Zephyr, but also allows users to specify custom MODULE_EXT_ROOTs for glue code using either `-DMODULE_EXT_ROOT` or `zephyr/module.yml` with `build:settings:module_ext_root` settings. MODULE_EXT_ROOT' is a list of directories, similar to other roots such as BOARD_ROOT, DTS_ROOT, etc. The Zephyr repo folder ${ZEPHYR_BASE} is always to the MODULE_EXT_ROOT list as lowest priority. For each MODULE_EXT_ROOT, the file `<module_ext_root>/modules/modules.cmake` will be processed. In Zephyr repo, the folder `modules/<module>/` contains CMakeLists.txt and Kconfig glue code for the Zephyr module. A Zephyr module can specify that CMakeLists.txt and Kconfig glue code is placed in an external module root by specifying: ``` build: cmake-ext: True kconfig-ext: True ``` It is still possible to place the CMakeLists.txt and Kconfig files directly in the Zephyr module using the existing: ``` build: cmake: <path> kconfig: <file> ```. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-12-17 18:27:42 +08:00
set(ZEPHYR_${MODULE_NAME_UPPER}_CMAKE_DIR ${module_dir})
endforeach()
file(GLOB kconfig_modules "${CMAKE_CURRENT_LIST_DIR}/*/Kconfig")
foreach(module ${kconfig_modules})
get_filename_component(module_dir ${module} DIRECTORY)
get_filename_component(module_name ${module_dir} NAME)
cmake: zephyr modules: sanitize all module name when used as variable The introduction of Zephyr module glue code in the Zephyr repository introduces a Kconfig variable in the form of: `config ZEPHYR_<MODULE_NAME>_MODULE`. All Kconfig variables go into `autoconf.h`, therefore it is necessary to sanitize the Kconfig variable, so that it does not contain special characters. To ensure consistent variable name, then the module name will be sanitized in all variable use in both Kconfig and CMake. The sanitization is done be replacing all special characters with an underscore, `_`. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-01-19 19:01:38 +08:00
zephyr_string(SANITIZE TOUPPER MODULE_NAME_UPPER ${module_name})
modules: introducing MODULE_EXT_ROOT to allow glue code in Zephyr repo This commit introduces MODULE_EXT_ROOT which allows CMake and Kconfig glue code to be placed outside of the Zephyr module repository. This allows for placing glue code in Zephyr, but also allows users to specify custom MODULE_EXT_ROOTs for glue code using either `-DMODULE_EXT_ROOT` or `zephyr/module.yml` with `build:settings:module_ext_root` settings. MODULE_EXT_ROOT' is a list of directories, similar to other roots such as BOARD_ROOT, DTS_ROOT, etc. The Zephyr repo folder ${ZEPHYR_BASE} is always to the MODULE_EXT_ROOT list as lowest priority. For each MODULE_EXT_ROOT, the file `<module_ext_root>/modules/modules.cmake` will be processed. In Zephyr repo, the folder `modules/<module>/` contains CMakeLists.txt and Kconfig glue code for the Zephyr module. A Zephyr module can specify that CMakeLists.txt and Kconfig glue code is placed in an external module root by specifying: ``` build: cmake-ext: True kconfig-ext: True ``` It is still possible to place the CMakeLists.txt and Kconfig files directly in the Zephyr module using the existing: ``` build: cmake: <path> kconfig: <file> ```. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-12-17 18:27:42 +08:00
set(ZEPHYR_${MODULE_NAME_UPPER}_KCONFIG ${module_dir}/Kconfig)
endforeach()