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

101 lines
2.9 KiB
CMake
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
toolchains: move zephyr sdk host tools to toolchain folder Should be part of other files related to the Zephyr SDK. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-01-15 00:21:23 +08:00
include(${ZEPHYR_BASE}/cmake/toolchain/zephyr/host-tools.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
cmake: Use west installation directly Since we install west from pip and it becomes an executable, use it directly assuming it's in the user's PATH. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Torsten Rasmussen <torsten.rasmussen@nordicsemi.no>
2018-11-12 22:23:51 +08:00
# west is optional
find_program(
WEST
west
)
if(${WEST} STREQUAL WEST-NOTFOUND)
unset(WEST)
cmake: add west version checking Parse the west version output and make sure both bootstrapper and installation wests are up to date. This will still work after the two are combined into what gets installed via PyPI. Fixes: #13209 Signed-off-by: Marti Bolivar <marti@foundries.io>
2019-03-12 04:42:31 +08:00
else()
# If west is found, make sure its version matches the minimum
# required one.
west: require v0.6.0 or higher The main change is the elimination of the bootstrapper, a design flaw / misfeature. Update the documentation to be compatible with the 0.6.x releases as well. This has to be done atomically, as there were incompatible changes. Make use of the versionchanged and versionadded directives to begin keeping track of how these APIs are evolving. (Note that west 0.6.0 will remain compatible with the extension commands in Zephyr v1.14 LTS as long as that is still alive. This change is targeted towards Zephyr 2.0 users.) This requires a bump in the shippable container and allows us to simplify the west_commands test procedure. Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
2019-07-23 01:00:59 +08:00
set(MIN_WEST_VERSION 0.6.0)
cmake: add west version checking Parse the west version output and make sure both bootstrapper and installation wests are up to date. This will still work after the two are combined into what gets installed via PyPI. Fixes: #13209 Signed-off-by: Marti Bolivar <marti@foundries.io>
2019-03-12 04:42:31 +08:00
execute_process(
COMMAND
cmake: Speed up CMake by not invoking 'west' Speed up CMake by 100ms by importing west instead of invoking it as an executable. There is significant overhead in invoking west as a script via pip. The exact reason why is not clear. Also, simplify the version output parsing as we get the version in a more machine-readable form now. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2019-11-05 23:54:20 +08:00
${PYTHON_EXECUTABLE}
-c
"import west.version; print(west.version.__version__, end='')"
OUTPUT_VARIABLE west_version
RESULT_VARIABLE west_version_output_result
cmake: add west version checking Parse the west version output and make sure both bootstrapper and installation wests are up to date. This will still work after the two are combined into what gets installed via PyPI. Fixes: #13209 Signed-off-by: Marti Bolivar <marti@foundries.io>
2019-03-12 04:42:31 +08:00
)
cmake: Speed up CMake by not invoking 'west' Speed up CMake by 100ms by importing west instead of invoking it as an executable. There is significant overhead in invoking west as a script via pip. The exact reason why is not clear. Also, simplify the version output parsing as we get the version in a more machine-readable form now. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2019-11-05 23:54:20 +08:00
if(west_version_output_result)
message(FATAL_ERROR "Unable to import west.version from '${PYTHON_EXECUTABLE}'")
endif()
if(${west_version} VERSION_LESS ${MIN_WEST_VERSION})
message(FATAL_ERROR "The detected west version is unsupported.\n\
cmake: add west version checking Parse the west version output and make sure both bootstrapper and installation wests are up to date. This will still work after the two are combined into what gets installed via PyPI. Fixes: #13209 Signed-off-by: Marti Bolivar <marti@foundries.io>
2019-03-12 04:42:31 +08:00
The version was found to be ${west_version}:\n\
${item}\n\
But the minimum supported version is ${MIN_WEST_VERSION}\n\
cmake: Speed up CMake by not invoking 'west' Speed up CMake by 100ms by importing west instead of invoking it as an executable. There is significant overhead in invoking west as a script via pip. The exact reason why is not clear. Also, simplify the version output parsing as we get the version in a more machine-readable form now. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2019-11-05 23:54:20 +08:00
Please upgrade with:\n\
pip3 install --upgrade west")
endif()
cmake: add west version checking Parse the west version output and make sure both bootstrapper and installation wests are up to date. This will still work after the two are combined into what gets installed via PyPI. Fixes: #13209 Signed-off-by: Marti Bolivar <marti@foundries.io>
2019-03-12 04:42:31 +08:00
# Just output information for a single version. This will still work
# even after output is one line.
message(STATUS "Found west: ${WEST} (found suitable version \"${west_version}\", minimum required is \"${MIN_WEST_VERSION}\")")
cmake: -fmacro-prefix-map=${WEST_TOPDIR}=WEST_TOPDIR Commit 28a5657f1ff6d and f67dcdbdf893a86 stopped ZEPHYR_BASE and CMAKE_SOURCE_DIR from leaking into __FILE__ and other macros. WEST_TOPDIR was still missing. Add it now that the new 'west topdir' command has been implemented in https://github.com/zephyrproject-rtos/west/pull/311 If the west version is too old then do nothing; same as before. Any ASSERT in a zephyr module outside ZEPHYR_BASE is enough to test this. One example: $ZEPHYR_BASE/sanitycheck -T $ZEPHYR_BASE/tests/posix/fs/ -p qemu_x86 -v readelf --string-dump=.rodata.disk_status.str1.1 {} \ $(find sanity-out -name zfs_diskio.c.obj | head -n 1) String dump of section '.rodata.disk_status.str1.1': [ 0] WEST_TOPDIR/modules/fs/fatfs/zfs_diskio.c [ 2a] pdrv < ((long) (((int) sizeof(char[1 - 2 * !(!__built.... [ de] ASSERTION FAIL [%s] @ %s:%d^J Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2019-06-12 07:57:37 +08:00
if (${west_version} VERSION_GREATER_EQUAL "0.7.0")
execute_process(
COMMAND ${WEST} topdir
OUTPUT_VARIABLE WEST_TOPDIR
OUTPUT_STRIP_TRAILING_WHITESPACE
)
endif()
cmake: Use west installation directly Since we install west from pip and it becomes an executable, use it directly assuming it's in the user's PATH. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> Signed-off-by: Torsten Rasmussen <torsten.rasmussen@nordicsemi.no>
2018-11-12 22:23:51 +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
# Search for the must-have program dtc on PATH and in
# TOOLCHAIN_HOME. Usually DTC will be provided by an SDK, but for
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
# SDK-less projects like gnuarmemb, it is up to the user to install
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
# dtc.
find_program(
DTC
dtc
)
if(${DTC} STREQUAL DTC-NOTFOUND)
message(FATAL_ERROR "Unable to find dtc")
endif()
cmake: Enforce that the DTC is at least 1.4.6 The Zephyr SDK distributes a device-tree-compiler with version "1.4.6-dirty". As of recently, we have started using flags that are only present in recent versions of dtc. Like the flag "-E unit_address_vs_reg". Users that are opting out of using the Zephyr SDK's host tools are reporting obscure error messages. To avoid this we use an appropriate error message when the detected version is unsupported. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-10-18 19:13:03 +08:00
# Parse the 'dtc --version' and make sure it is at least MIN_DTC_VERSION
set(MIN_DTC_VERSION 1.4.6)
execute_process(
COMMAND
${DTC} --version
OUTPUT_VARIABLE dtc_version_output
)
string(REGEX MATCH "Version: DTC ([0-9]+\.[0-9]+.[0-9]+).*" out_var ${dtc_version_output})
if(${CMAKE_MATCH_1} VERSION_LESS ${MIN_DTC_VERSION})
assert(0 "The detected dtc version is unsupported. \n\
cmake: Whitespace and commentary fixes Cosmetics, no functional change expected. Fixed leading space alignment. Replaced tabs with spaces. Emulation error message output is now aligned. To locate tabs in cmake, the following bash is useful: grep -PRil "\t" * | grep -i cmake | grep -v ^sanity Signed-off-by: Mark Ruvald Pedersen <mped@oticon.com>
2018-12-19 17:40:57 +08:00
The version was found to be ${CMAKE_MATCH_1} \n\
But the minimum supported version is ${MIN_DTC_VERSION} \n\
doc: restructure and create index pages Move all lead pages to be index pages and create redirect rules from the old pointers. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-02-04 06:29:46 +08:00
See https://docs.zephyrproject.org/latest/getting_started/ \n\
cmake: Whitespace and commentary fixes Cosmetics, no functional change expected. Fixed leading space alignment. Replaced tabs with spaces. Emulation error message output is now aligned. To locate tabs in cmake, the following bash is useful: grep -PRil "\t" * | grep -i cmake | grep -v ^sanity Signed-off-by: Mark Ruvald Pedersen <mped@oticon.com>
2018-12-19 17:40:57 +08:00
for how to use the SDK's dtc alongside a custom toolchain."
)
cmake: Enforce that the DTC is at least 1.4.6 The Zephyr SDK distributes a device-tree-compiler with version "1.4.6-dirty". As of recently, we have started using flags that are only present in recent versions of dtc. Like the flag "-E unit_address_vs_reg". Users that are opting out of using the Zephyr SDK's host tools are reporting obscure error messages. To avoid this we use an appropriate error message when the detected version is unsupported. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
2018-10-18 19:13:03 +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
find_program(
GPERF
gperf
)
if(${GPERF} STREQUAL GPERF-NOTFOUND)
message(FATAL_ERROR "Unable to find gperf")
endif()
cmake: Fixed openocd Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no>
2017-11-09 02:20:55 +08:00
# openocd is an optional dependency
find_program(
OPENOCD
openocd
)
boards: common: bossac: Fix bossac flash script. The flash script was broken after the cmake changes. Updated the path needed for the flash scripts. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-06-01 14:37:28 +08:00
# bossac is an optional dependency
find_program(
BOSSAC
bossac
)
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: Should we instead find one qemu binary for each ARCH?
# TODO: This will probably need to be re-organized when there exists more than one SDK.