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

134 lines
4.4 KiB
CMake
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 21:43:34 +08:00
# Zephyr code can configure itself based on a KConfig'uration with the
# header file autoconf.h. There exists an analogous file
# generated_dts_board.h that allows configuration based on information
# encoded in DTS.
#
# Here we call on dtc, the gcc preprocessor, and
# scripts/dts/extract_dts_includes.py to generate this header file at
# CMake configure-time.
#
# See ~/zephyr/doc/dts
set(GENERATED_DTS_BOARD_H ${PROJECT_BINARY_DIR}/include/generated/generated_dts_board.h)
set(GENERATED_DTS_BOARD_CONF ${PROJECT_BINARY_DIR}/include/generated/generated_dts_board.conf)
cmake: dts: Fix usage of BOARD vs BOARD_FAMILY We assumed that ${BOARD} and ${BOARD_FAMILY} are always the same and thus interchangeable. That isn't always the case so use ${BOARD} proper for when we mean the exact BOARD name we are building for vs the BOARD_FAMILY. We also add .dts files for board variants within a board family, such that we have a .dts matching each board name. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-02-27 00:52:29 +08:00
set_ifndef(DTS_SOURCE ${BOARD_ROOT}/boards/${ARCH}/${BOARD_FAMILY}/${BOARD}.dts)
cmake: replace PROJECT_SOURCE_DIR with ZEPHYR_BASE Both variables were used (with the same value) interchangeably throughout CMake files and per the discussion in GH issue, ZEPHYR_BASE is preferred. Also add a comment with explanation of one vs. the other. Tested by building hello_world for several boards ensuring no errors. Fixes #7173. Signed-off-by: Alex Tereschenko <alext.mkrs@gmail.com>
2018-06-15 02:21:18 +08:00
set_ifndef(DTS_COMMON_OVERLAYS ${ZEPHYR_BASE}/dts/common/common.dts)
dts: bindings: scan application dir for bindings In addtion to zephyr/dts/bindings als scan the dts/bindings directory within the application source directory for bindings. Allows to have application specific bindings and drivers. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
2018-08-21 17:02:48 +08:00
set_ifndef(DTS_APP_BINDINGS ${APPLICATION_SOURCE_DIR}/dts/bindings)
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
message(STATUS "Generating zephyr/include/generated/generated_dts_board.h")
if(CONFIG_HAS_DTS)
cmake: dts: Allow multiple overlay files This patch changes the manner in which we collect DTS overlay files so that they comply with the same approach taken for configuration fragment files (.conf). Additionally it also documents the usage of those files in the Application Developer Guide. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-02-01 01:00:49 +08:00
if(DTC_OVERLAY_FILE)
# Convert from space-separated files into file list
string(REPLACE " " ";" DTC_OVERLAY_FILE_AS_LIST ${DTC_OVERLAY_FILE})
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
endif()
dts: mcuboot: Support for common overlays and mcuboot When the Kconfig BOOTLOADER_MCUBOOT is selected, an overlay to place the image at the slot0 location is required. In order to avoid having to do this manually for all samples when targetting MCUboot, include the logic inside the dts.cmake script to prepend a new common.dts file that then conditionally includes mcuboot.overlay. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-02-07 19:37:56 +08:00
# Prepend common overlays
set(DTC_OVERLAY_FILE_AS_LIST ${DTS_COMMON_OVERLAYS} ${DTC_OVERLAY_FILE_AS_LIST})
cmake: dts: Allow multiple overlay files This patch changes the manner in which we collect DTS overlay files so that they comply with the same approach taken for configuration fragment files (.conf). Additionally it also documents the usage of those files in the Application Developer Guide. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-02-01 01:00:49 +08:00
set(
dts_files
${DTS_SOURCE}
${DTC_OVERLAY_FILE_AS_LIST}
)
unset(DTC_INCLUDE_FLAG_FOR_DTS)
foreach(dts_file ${dts_files})
list(APPEND DTC_INCLUDE_FLAG_FOR_DTS
-include ${dts_file})
endforeach()
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
# TODO: Cut down on CMake configuration time by avoiding
# regeneration of generated_dts_board.h on every configure. How
# challenging is this? What are the dts dependencies? We run the
# preprocessor, and it seems to be including all kinds of
# directories with who-knows how many header files.
# Run the C preprocessor on an empty C source file that has one or
# more DTS source files -include'd into it to create the
# intermediary file *.dts.pre.tmp
execute_process(
COMMAND ${CMAKE_C_COMPILER}
-x assembler-with-cpp
-nostdinc
soc: adapt Kconfig/CMake for soc in top / Change build system to point to soc/ in the top directory rather than under arch/ Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-09-04 04:20:14 +08:00
-I${ZEPHYR_BASE}/soc/${ARCH}
cmake: replace PROJECT_SOURCE_DIR with ZEPHYR_BASE Both variables were used (with the same value) interchangeably throughout CMake files and per the discussion in GH issue, ZEPHYR_BASE is preferred. Also add a comment with explanation of one vs. the other. Tested by building hello_world for several boards ensuring no errors. Fixes #7173. Signed-off-by: Alex Tereschenko <alext.mkrs@gmail.com>
2018-06-15 02:21:18 +08:00
-isystem ${ZEPHYR_BASE}/include
-isystem ${ZEPHYR_BASE}/dts/${ARCH}
-isystem ${ZEPHYR_BASE}/dts
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
-include ${AUTOCONF_H}
cmake: dts: Allow multiple overlay files This patch changes the manner in which we collect DTS overlay files so that they comply with the same approach taken for configuration fragment files (.conf). Additionally it also documents the usage of those files in the Application Developer Guide. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-02-01 01:00:49 +08:00
${DTC_INCLUDE_FLAG_FOR_DTS} # include the DTS source and overlays
cmake: replace PROJECT_SOURCE_DIR with ZEPHYR_BASE Both variables were used (with the same value) interchangeably throughout CMake files and per the discussion in GH issue, ZEPHYR_BASE is preferred. Also add a comment with explanation of one vs. the other. Tested by building hello_world for several boards ensuring no errors. Fixes #7173. Signed-off-by: Alex Tereschenko <alext.mkrs@gmail.com>
2018-06-15 02:21:18 +08:00
-I${ZEPHYR_BASE}/dts/common
-I${ZEPHYR_BASE}/drivers
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
-undef -D__DTS__
-P
cmake: Use path-corrected version of ZEPHYR_BASE Instead of accessing the environment variable ZEPHYR_BASE every time we require accessing the source code root, use an intermediate variable that has OS path separators correctly set to '/' to avoid issues on Windows. Note: This removes the ZEPHYR_SOURCE_DIR CMake variable. External applications using that will need to change to use the new ZEPHYR_BASE variable. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-01-11 22:46:44 +08:00
-E ${ZEPHYR_BASE}/misc/empty_file.c
cmake: dts: Fix usage of BOARD vs BOARD_FAMILY We assumed that ${BOARD} and ${BOARD_FAMILY} are always the same and thus interchangeable. That isn't always the case so use ${BOARD} proper for when we mean the exact BOARD name we are building for vs the BOARD_FAMILY. We also add .dts files for board variants within a board family, such that we have a .dts matching each board name. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-02-27 00:52:29 +08:00
-o ${BOARD}.dts.pre.tmp
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
WORKING_DIRECTORY ${PROJECT_BINARY_DIR}
RESULT_VARIABLE ret
)
if(NOT "${ret}" STREQUAL "0")
message(FATAL_ERROR "command failed with return code: ${ret}")
endif()
# Run the DTC on *.dts.pre.tmp to create the intermediary file *.dts_compiled
execute_process(
COMMAND ${DTC}
-O dts
cmake: dts: Fix usage of BOARD vs BOARD_FAMILY We assumed that ${BOARD} and ${BOARD_FAMILY} are always the same and thus interchangeable. That isn't always the case so use ${BOARD} proper for when we mean the exact BOARD name we are building for vs the BOARD_FAMILY. We also add .dts files for board variants within a board family, such that we have a .dts matching each board name. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-02-27 00:52:29 +08:00
-o ${BOARD}.dts_compiled
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
-b 0
cmake: dts: Fix usage of BOARD vs BOARD_FAMILY We assumed that ${BOARD} and ${BOARD_FAMILY} are always the same and thus interchangeable. That isn't always the case so use ${BOARD} proper for when we mean the exact BOARD name we are building for vs the BOARD_FAMILY. We also add .dts files for board variants within a board family, such that we have a .dts matching each board name. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-02-27 00:52:29 +08:00
${BOARD}.dts.pre.tmp
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
WORKING_DIRECTORY ${PROJECT_BINARY_DIR}
RESULT_VARIABLE ret
)
if(NOT "${ret}" STREQUAL "0")
message(FATAL_ERROR "command failed with return code: ${ret}")
endif()
# Run extract_dts_includes.py for the header file
# generated_dts_board.h
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-12 12:30:57 +08:00
set_ifndef(DTS_BOARD_FIXUP_FILE ${BOARD_ROOT}/boards/${ARCH}/${BOARD_FAMILY}/dts.fixup)
cmake: dts: rename dts fixup file related variables Rename the variables related to DTS fixup to be clear what they are used for. This also lets us introduce a SOC level DTS fixup in the future that is distinct from the board one. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-11-09 23:50:07 +08:00
if(EXISTS ${DTS_BOARD_FIXUP_FILE})
scripts/dts: Make extract_dts_includes generating both files by itself Thus no need to parse twice the .dtsi, .dts and .yaml files. Simplify provided arguments relevancy, letting argparse generating usage message by itself. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-03-07 18:15:00 +08:00
set(DTS_BOARD_FIXUP ${DTS_BOARD_FIXUP_FILE})
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
endif()
build: support out of tree SoC definition Add the glue to make this work with SoC code outside of the tree. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-09-05 03:34:06 +08:00
set_ifndef(DTS_SOC_FIXUP_FILE ${SOC_DIR}/${ARCH}/${SOC_PATH}/dts.fixup)
dts: add support for soc family level fixups We duplicate a lot of fixup info per board which could be done at the SoC family level. So introduce the concept of DTS_SOC_FIXUP_FILE which we default to arch/<ARCH>/soc/<SOC_FAMILY>/<SOC_SERIES>/dts.fixup. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-01-24 03:30:30 +08:00
if(EXISTS ${DTS_SOC_FIXUP_FILE})
scripts/dts: Make extract_dts_includes generating both files by itself Thus no need to parse twice the .dtsi, .dts and .yaml files. Simplify provided arguments relevancy, letting argparse generating usage message by itself. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-03-07 18:15:00 +08:00
set(DTS_SOC_FIXUP ${DTS_SOC_FIXUP_FILE})
dts: add support for soc family level fixups We duplicate a lot of fixup info per board which could be done at the SoC family level. So introduce the concept of DTS_SOC_FIXUP_FILE which we default to arch/<ARCH>/soc/<SOC_FAMILY>/<SOC_SERIES>/dts.fixup. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-01-24 03:30:30 +08:00
endif()
dts: add support for application level dts.fixup We allow the application to have its own dts.fixup. The main use for this right now is for the build all test to define dummy values for defines we expect to be generated. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-01-27 01:24:13 +08:00
if(EXISTS ${APPLICATION_SOURCE_DIR}/dts.fixup)
scripts/dts: Make extract_dts_includes generating both files by itself Thus no need to parse twice the .dtsi, .dts and .yaml files. Simplify provided arguments relevancy, letting argparse generating usage message by itself. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-03-07 18:15:00 +08:00
set(DTS_APP_FIXUP ${APPLICATION_SOURCE_DIR}/dts.fixup)
dts: add support for application level dts.fixup We allow the application to have its own dts.fixup. The main use for this right now is for the build all test to define dummy values for defines we expect to be generated. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-01-27 01:24:13 +08:00
endif()
scripts/dts: Make extract_dts_includes generating both files by itself Thus no need to parse twice the .dtsi, .dts and .yaml files. Simplify provided arguments relevancy, letting argparse generating usage message by itself. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-03-07 18:15:00 +08:00
set(DTS_FIXUPS ${DTS_SOC_FIXUP} ${DTS_BOARD_FIXUP} ${DTS_APP_FIXUP})
if(NOT "${DTS_FIXUPS}" STREQUAL "")
set(DTS_FIXUPS --fixup ${DTS_FIXUPS})
endif()
dts: bindings: scan application dir for bindings In addtion to zephyr/dts/bindings als scan the dts/bindings directory within the application source directory for bindings. Allows to have application specific bindings and drivers. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
2018-08-21 17:02:48 +08:00
if(NOT EXISTS ${DTS_APP_BINDINGS})
set(DTS_APP_BINDINGS)
endif()
cmake: replace PROJECT_SOURCE_DIR with ZEPHYR_BASE Both variables were used (with the same value) interchangeably throughout CMake files and per the discussion in GH issue, ZEPHYR_BASE is preferred. Also add a comment with explanation of one vs. the other. Tested by building hello_world for several boards ensuring no errors. Fixes #7173. Signed-off-by: Alex Tereschenko <alext.mkrs@gmail.com>
2018-06-15 02:21:18 +08:00
set(CMD_EXTRACT_DTS_INCLUDES ${PYTHON_EXECUTABLE} ${ZEPHYR_BASE}/scripts/dts/extract_dts_includes.py
cmake: dts: Fix usage of BOARD vs BOARD_FAMILY We assumed that ${BOARD} and ${BOARD_FAMILY} are always the same and thus interchangeable. That isn't always the case so use ${BOARD} proper for when we mean the exact BOARD name we are building for vs the BOARD_FAMILY. We also add .dts files for board variants within a board family, such that we have a .dts matching each board name. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-02-27 00:52:29 +08:00
--dts ${BOARD}.dts_compiled
dts: bindings: scan application dir for bindings In addtion to zephyr/dts/bindings als scan the dts/bindings directory within the application source directory for bindings. Allows to have application specific bindings and drivers. Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
2018-08-21 17:02:48 +08:00
--yaml ${ZEPHYR_BASE}/dts/bindings ${DTS_APP_BINDINGS}
scripts/dts: Make extract_dts_includes generating both files by itself Thus no need to parse twice the .dtsi, .dts and .yaml files. Simplify provided arguments relevancy, letting argparse generating usage message by itself. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-03-07 18:15:00 +08:00
${DTS_FIXUPS}
--keyvalue ${GENERATED_DTS_BOARD_CONF}
--include ${GENERATED_DTS_BOARD_H}
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
)
scripts/dts: Make extract_dts_includes generating both files by itself Thus no need to parse twice the .dtsi, .dts and .yaml files. Simplify provided arguments relevancy, letting argparse generating usage message by itself. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-03-07 18:15:00 +08:00
# Run extract_dts_includes.py to create a .conf and a header file that can be
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
# included into the CMake namespace
execute_process(
scripts/dts: Make extract_dts_includes generating both files by itself Thus no need to parse twice the .dtsi, .dts and .yaml files. Simplify provided arguments relevancy, letting argparse generating usage message by itself. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2018-03-07 18:15:00 +08:00
COMMAND ${CMD_EXTRACT_DTS_INCLUDES}
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
WORKING_DIRECTORY ${PROJECT_BINARY_DIR}
RESULT_VARIABLE ret
)
if(NOT "${ret}" STREQUAL "0")
message(FATAL_ERROR "command failed with return code: ${ret}")
endif()
import_kconfig(${GENERATED_DTS_BOARD_CONF})
else()
file(WRITE ${GENERATED_DTS_BOARD_H} "/* WARNING. THIS FILE IS AUTO-GENERATED. DO NOT MODIFY! */")
endif()