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

72 lines
2.5 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
set(CMAKE_SYSTEM_NAME Generic)
set(CMAKE_SYSTEM_PROCESSOR ${ARCH})
set(BUILD_SHARED_LIBS OFF)
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY)
cmake: Don't use the environment variable CFLAGS Some distros set the environment variable CFLAGS, this will accidentally affect Zephyr builds. To fix this we clear the environment variable from within the Zephyr build system for the duration of the CMake execution. Until now we have been instructing the user to clear it, but it is easier for the user if we clear it for him. The same applies to CXXFLAGS. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-09-03 16:54:16 +08:00
# Don't inherit compiler flags from the environment
foreach(var CFLAGS CXXFLAGS)
if(DEFINED ENV{${var}})
message(WARNING "The environment variable '${var}' was set to $ENV{${var}},
but Zephyr ignores flags from the environment. Use 'cmake -DEXTRA_${var}=$ENV{${var}}' instead.")
unset(ENV{${var}})
endif()
endforeach()
build: deprecate ZEPHYR_GCC_VARIANT We want to support other toolchain not based on GCC, so the variable is confusing, use ZEPHYR_TOOLCHAIN_VARIANT instead. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-12 04:36:21 +08:00
# Until we completely deprecate it
cmake: toolchain: Don't warn of both ZEPHYR_*_VARIANT envvars defined Someone doing bisects on Zephyr will have to have both older ZEPHYR_GCC_VARIANT and newer ZEPHYR_TOOLCHAIN_VARIANT environment variables defined. Then warning about ZEPHYR_GCC_VARIANT is confusing. Issue it if only ZEPHYR_GCC_VARIANT is defined, and ZEPHYR_TOOLCHAIN_VARIANT isn't. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2018-05-31 01:52:27 +08:00
if(NOT DEFINED ENV{ZEPHYR_TOOLCHAIN_VARIANT})
if(DEFINED ENV{ZEPHYR_GCC_VARIANT})
message(WARNING "ZEPHYR_GCC_VARIANT is deprecated, please use ZEPHYR_TOOLCHAIN_VARIANT instead")
set(ZEPHYR_TOOLCHAIN_VARIANT $ENV{ZEPHYR_GCC_VARIANT})
endif()
build: deprecate ZEPHYR_GCC_VARIANT We want to support other toolchain not based on GCC, so the variable is confusing, use ZEPHYR_TOOLCHAIN_VARIANT instead. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-12 04:36:21 +08:00
endif()
if(NOT ZEPHYR_TOOLCHAIN_VARIANT)
if(DEFINED ENV{ZEPHYR_TOOLCHAIN_VARIANT})
set(ZEPHYR_TOOLCHAIN_VARIANT $ENV{ZEPHYR_TOOLCHAIN_VARIANT})
cmake: Re-introduce support for CROSS_COMPILE CROSS_COMPILE is a KBuild feature that was dropped during the CMake migration. It is now re-introduced. Documentation for it is still lacking, but at least it now behaves as expected. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-01-09 00:06:42 +08:00
elseif(CROSS_COMPILE OR CONFIG_CROSS_COMPILE OR (DEFINED ENV{CROSS_COMPILE}))
build: deprecate ZEPHYR_GCC_VARIANT We want to support other toolchain not based on GCC, so the variable is confusing, use ZEPHYR_TOOLCHAIN_VARIANT instead. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-12 04:36:21 +08:00
set(ZEPHYR_TOOLCHAIN_VARIANT cross-compile)
cmake: Re-introduce support for CROSS_COMPILE CROSS_COMPILE is a KBuild feature that was dropped during the CMake migration. It is now re-introduced. Documentation for it is still lacking, but at least it now behaves as expected. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-01-09 00:06:42 +08:00
endif()
endif()
build: Replace GCC ARM Embedded with GNU Arm Embedded The old GCC ARM Embedded website on launchpad (https://launchpad.net/gcc-arm-embedded) has been superseeded by the new GNU Arm Embedded one (https://developer.arm.com/open-source/gnu-toolchain/gnu-rm). This also means a change of name from "GCC" to "GNU". Reflect this in the enviroment variables so that the proper term is used henceforth. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-08-03 23:11:23 +08:00
# Until we completely deprecate it
cmake: Add quotes to handle missing ZEPHYR_TOOLCHAIN_VARIANT variable If this environment variable is missing, the user gets a rather confusing cmake error message about "STREQUAL" "gccarmemb" from the lines below. Adding quotes to the check makes cmake handle it better and instead report the problem in the later ASSERT. Signed-off-by: Björn Stenberg <bjorn@haxx.se>
2018-09-24 19:50:25 +08:00
if("${ZEPHYR_TOOLCHAIN_VARIANT}" STREQUAL "gccarmemb")
build: Replace GCC ARM Embedded with GNU Arm Embedded The old GCC ARM Embedded website on launchpad (https://launchpad.net/gcc-arm-embedded) has been superseeded by the new GNU Arm Embedded one (https://developer.arm.com/open-source/gnu-toolchain/gnu-rm). This also means a change of name from "GCC" to "GNU". Reflect this in the enviroment variables so that the proper term is used henceforth. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-08-03 23:11:23 +08:00
message(WARNING "gccarmemb is deprecated, please use gnuarmemb instead")
set(ZEPHYR_TOOLCHAIN_VARIANT "gnuarmemb")
endif()
build: deprecate ZEPHYR_GCC_VARIANT We want to support other toolchain not based on GCC, so the variable is confusing, use ZEPHYR_TOOLCHAIN_VARIANT instead. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-12 04:36:21 +08:00
set(ZEPHYR_TOOLCHAIN_VARIANT ${ZEPHYR_TOOLCHAIN_VARIANT} CACHE STRING "Zephyr toolchain variant")
assert(ZEPHYR_TOOLCHAIN_VARIANT "Zephyr toolchain variant invalid: please set the ZEPHYR_TOOLCHAIN_VARIANT-variable")
cmake: Re-introduce support for CROSS_COMPILE CROSS_COMPILE is a KBuild feature that was dropped during the CMake migration. It is now re-introduced. Documentation for it is still lacking, but at least it now behaves as expected. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-01-09 00:06:42 +08:00
build: deprecate ZEPHYR_GCC_VARIANT We want to support other toolchain not based on GCC, so the variable is confusing, use ZEPHYR_TOOLCHAIN_VARIANT instead. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-12 04:36:21 +08:00
if(CONFIG_ARCH_POSIX OR (ZEPHYR_TOOLCHAIN_VARIANT STREQUAL "host"))
cmake: Re-introduce support for CROSS_COMPILE CROSS_COMPILE is a KBuild feature that was dropped during the CMake migration. It is now re-introduced. Documentation for it is still lacking, but at least it now behaves as expected. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-01-09 00:06:42 +08:00
set(COMPILER host-gcc)
endif()
build: Replace GCC ARM Embedded with GNU Arm Embedded The old GCC ARM Embedded website on launchpad (https://launchpad.net/gcc-arm-embedded) has been superseeded by the new GNU Arm Embedded one (https://developer.arm.com/open-source/gnu-toolchain/gnu-rm). This also means a change of name from "GCC" to "GNU". Reflect this in the enviroment variables so that the proper term is used henceforth. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-08-03 23:11:23 +08:00
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
# Configure the toolchain based on what SDK/toolchain is in use.
cmake: Re-introduce support for CROSS_COMPILE CROSS_COMPILE is a KBuild feature that was dropped during the CMake migration. It is now re-introduced. Documentation for it is still lacking, but at least it now behaves as expected. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-01-09 00:06:42 +08:00
if(NOT (COMPILER STREQUAL "host-gcc"))
toolchain: organise toolchain/compiler files Move toolchain definitions into toolchain/ and move compilers to compilers/ Usage of toolchain- for everything was confusing, there are the actual compiler related definitions and there is the toolchain/SDK related configs, so keeping them separate helps understand the different and prevents confusion. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-12 04:47:59 +08:00
include(${ZEPHYR_BASE}/cmake/toolchain/${ZEPHYR_TOOLCHAIN_VARIANT}.cmake)
arch: native: Run Zephyr natively in a POSIX OS A new arch (posix) which relies on pthreads to emulate the context switching A new soc for it (inf_clock) which emulates a CPU running at an infinely high clock (so when the CPU is awaken it runs till completion in 0 time) A new board, which provides a trivial system tick timer and irq generation. Origin: Original Fixes #1891 Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-10-03 22:31:55 +08:00
endif()
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
# Configure the toolchain based on what toolchain technology is used
cmake: toolchain: Misc. comment cleanups Sync the outdated comments with the code. E.g. there is no toolchain-clang.cmake, but there is a toolchain-host-gcc.cmake. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-01-09 00:05:26 +08:00
# (gcc, host-gcc etc.)
toolchain: organise toolchain/compiler files Move toolchain definitions into toolchain/ and move compilers to compilers/ Usage of toolchain- for everything was confusing, there are the actual compiler related definitions and there is the toolchain/SDK related configs, so keeping them separate helps understand the different and prevents confusion. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-12 04:47:59 +08:00
include(${ZEPHYR_BASE}/cmake/compiler/${COMPILER}.cmake OPTIONAL)
cmake: toolchain: Checksum the toolchain to uniquely identify it This commit introduces TOOLCHAIN_SIGNATURE. A CMake variable that is defined like this: Toolchains with the same signature will always support the same set of flags. Currently it is implemented by MD5summing the CC binary. This is useful for instance if the build system needs to determine if it has seen the toolchain before, e.g. in a caching use-case. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-04-17 20:49:52 +08:00
# Uniquely identify the toolchain wrt. it's capabilities.
#
# What we are looking for, is a signature definition that is defined
# like this:
# Toolchains with the same signature will always support the same set
# of flags.
# It is not clear how this signature should be constructed. The
# strategy chosen is to md5sum the CC binary.
file(MD5 ${CMAKE_C_COMPILER} CMAKE_C_COMPILER_MD5_SUM)
set(TOOLCHAIN_SIGNATURE ${CMAKE_C_COMPILER_MD5_SUM})