zephyr/cmake/usage/CMakeLists.txt

string(REPLACE ";" " " BOARD_ROOT_SPACE_SEPARATED "${BOARD_ROOT}")

add_custom_target(
  usage
  ${CMAKE_COMMAND}
  -DBOARD_ROOT_SPACE_SEPARATED=${BOARD_ROOT_SPACE_SEPARATED}
  -P ${CMAKE_CURRENT_SOURCE_DIR}/usage.cmake
  )

# NB: The reason it is 'usage' and not help is that CMake already
# defines a target 'help'
cmake: Fall back to ZEPHYR_BASE when the board is not in BOARD_ROOT It is very inconvenient to maintain an application that both runs on a Zephyr board and an out-of-tree board. It forces one to write build scripts like this in the app: if(BOARD STREQUAL my_out_of_tree_board) set(BOARD_ROOT some/out/of/tree/board/path) endif() To avoid this we change the semantics of BOARD_ROOT. Instead of it being a path to the board root it is now a prioritized list of board root directories. Zephyr will append ZEPHYR_BASE to BOARD_ROOT. This ensures that Zephyr boards can be used when the out-of-tree board directory can not supply the requested board. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no> 2018-09-28 00:10:22 +08:00			`string(REPLACE ";" " " BOARD_ROOT_SPACE_SEPARATED "${BOARD_ROOT}")`

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 21:43:34 +08:00			`add_custom_target(`
			`usage`
cmake: Fix printed list of supported boards. Fixes issue #7184. Use $BOARD_ROOT to find correct list of supported boards. This is needed since the user can set this variable to any directory. Pass $BOARD_ROOT to usage.cmake where it is called. Signed-off-by: Håkon Øye Amundsen <haakon.amundsen@nordicsemi.no> 2018-04-25 15:17:18 +08:00			`${CMAKE_COMMAND}`
cmake: Fall back to ZEPHYR_BASE when the board is not in BOARD_ROOT It is very inconvenient to maintain an application that both runs on a Zephyr board and an out-of-tree board. It forces one to write build scripts like this in the app: if(BOARD STREQUAL my_out_of_tree_board) set(BOARD_ROOT some/out/of/tree/board/path) endif() To avoid this we change the semantics of BOARD_ROOT. Instead of it being a path to the board root it is now a prioritized list of board root directories. Zephyr will append ZEPHYR_BASE to BOARD_ROOT. This ensures that Zephyr boards can be used when the out-of-tree board directory can not supply the requested board. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no> 2018-09-28 00:10:22 +08:00			`-DBOARD_ROOT_SPACE_SEPARATED=${BOARD_ROOT_SPACE_SEPARATED}`
cmake: Fix printed list of supported boards. Fixes issue #7184. Use $BOARD_ROOT to find correct list of supported boards. This is needed since the user can set this variable to any directory. Pass $BOARD_ROOT to usage.cmake where it is called. Signed-off-by: Håkon Øye Amundsen <haakon.amundsen@nordicsemi.no> 2018-04-25 15:17:18 +08:00			`-P ${CMAKE_CURRENT_SOURCE_DIR}/usage.cmake`
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 21:43:34 +08:00			`)`

			`# NB: The reason it is 'usage' and not help is that CMake already`
			`# defines a target 'help'`