michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/boards/CMakeLists.txt

13 lines
284 B
Text
Raw Normal View History

Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no>
2017-10-27 15:43:34 +02:00
# To avoid a lot of empty CMakeLists.txt files we assume it is not an
# error if it is missing
if(EXISTS ${BOARD_DIR}/CMakeLists.txt)
build: support out-of-tree custom boards This is one way we can support out of tree board definitions. Basically all this needs is a board definition in the application source directory that follows the same structure we have in the main Zephyr tree (also allowing multiple custom boards). An application tree would look like this for example: boards/ CMakeLists.txt prj.conf README.rst src/ with boards following the same structure as in Zephyr: . ├── boards │   └── x86 │   └── arduino_101 │   ├── doc │   │   └── img │   └── support └── src To use this, you need to specify the BOARD_ROOT variable on the command line when building: cmake -DBOARD=<board name> -DBOARD_ROOT=<path to boards> .. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-11 22:30:57 -06:00
if(BOARD_ROOT)
cmake: Misc. cleanups of how BOARD_ROOT and BOARD_DIR are used Misc. refactorings that clean up how BOARD_ROOT and BOARD_DIR are used. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-09-27 17:15:24 +02:00
set(build_dir boards/${ARCH}/${BOARD})
build: support out-of-tree custom boards This is one way we can support out of tree board definitions. Basically all this needs is a board definition in the application source directory that follows the same structure we have in the main Zephyr tree (also allowing multiple custom boards). An application tree would look like this for example: boards/ CMakeLists.txt prj.conf README.rst src/ with boards following the same structure as in Zephyr: . ├── boards │   └── x86 │   └── arduino_101 │   ├── doc │   │   └── img │   └── support └── src To use this, you need to specify the BOARD_ROOT variable on the command line when building: cmake -DBOARD=<board name> -DBOARD_ROOT=<path to boards> .. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-11 22:30:57 -06:00
else()
cmake: Misc. cleanups of how BOARD_ROOT and BOARD_DIR are used Misc. refactorings that clean up how BOARD_ROOT and BOARD_DIR are used. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-09-27 17:15:24 +02:00
unset(build_dir)
build: support out-of-tree custom boards This is one way we can support out of tree board definitions. Basically all this needs is a board definition in the application source directory that follows the same structure we have in the main Zephyr tree (also allowing multiple custom boards). An application tree would look like this for example: boards/ CMakeLists.txt prj.conf README.rst src/ with boards following the same structure as in Zephyr: . ├── boards │   └── x86 │   └── arduino_101 │   ├── doc │   │   └── img │   └── support └── src To use this, you need to specify the BOARD_ROOT variable on the command line when building: cmake -DBOARD=<board name> -DBOARD_ROOT=<path to boards> .. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-11 22:30:57 -06:00
endif()
cmake: Misc. cleanups of how BOARD_ROOT and BOARD_DIR are used Misc. refactorings that clean up how BOARD_ROOT and BOARD_DIR are used. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-09-27 17:15:24 +02:00
add_subdirectory(${BOARD_DIR} ${build_dir})
Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no>
2017-10-27 15:43:34 +02:00
endif()
Copy permalink