michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/tests/kernel/device/CMakeLists.txt

17 lines
660 B
CMake
Raw Permalink 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 15:08:09 +02:00
# SPDX-License-Identifier: Apache-2.0
cmake: increase minimal required version to 3.20.0 Move to CMake 3.20.0. At the Toolchain WG it was decided to move to CMake 3.20.0. The main reason for increasing CMake version is better toolchain support. Better toolchain support is added in the following CMake versions: - armclang, CMake 3.15 - Intel oneAPI, CMake 3.20 - IAR, CMake 3.15 and 3.20 Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-08-10 14:44:56 +02:00
cmake_minimum_required(VERSION 3.20.0)
tests: make find_package(Zephyr...) REQUIRED ... because it is (required). This makes a difference when building with CMake and forgetting ZEPHYR_BASE or not registering Zephyr in the CMake package registry. In this particular case, REQUIRED turns this harmless looking log statement: -- Could NOT find Zephyr (missing: Zephyr_DIR) -- The C compiler identification is GNU 9.3.0 -- The CXX compiler identification is GNU 9.3.0 -- Check for working C compiler: /usr/bin/cc -- ... -- ... -- ... -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at CMakeLists.txt:8 (target_sources): Cannot specify sources for target "app" which is not built by this project. ... into this louder, clearer, faster and (last but not least) final error: CMake Error at CMakeLists.txt:5 (find_package): Could not find a package configuration file provided by "Zephyr" with any of the following names: ZephyrConfig.cmake zephyr-config.cmake Add the installation prefix of "Zephyr" to CMAKE_PREFIX_PATH or set "Zephyr_DIR" to a directory containing one of the above files. If "Zephyr" provides a separate development package or SDK, be sure it has been installed. -- Configuring incomplete, errors occurred! Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-05-29 02:58:50 +02:00
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
samples, tests: Use semi-accurate project names When using an IDE (e.g. Eclipse, Qt Creator), the project name gets displayed. This greatly simplifies the navigation between projects when having many of them open at the same time. Naming every project "NONE" defeats this functionality. This patch tries to use sensible project names while not duplicating too much of what is already represented in the path. This is done by using the name of the directory the relevant CMakeLists.txt file is stored in. To ensure unique project names in the samples (and again, in the tests folder) folder, small manual adjustments have been done. Signed-off-by: Reto Schneider <code@reto-schneider.ch>
2018-10-25 16:54:09 +02:00
project(device)
tests: add test for device class/API Test APIs of device model and verify execution with power management enabled. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 05:36:01 +01:00
FILE(GLOB app_sources src/*.c)
target_sources(app PRIVATE ${app_sources})
tests/kernel/device: extends test for code coverage device_get_binding() compares pointers first before doing strcmp(). However, enabling coverage forces -O0 to disable any compiler optimizations. There would be multiple copies of the same string, and the code pathing doing pointer comparsion would not be tested at all. So add this flag to merge string constants such that the pointer comparison would be exercised. This also adds a bad driver which fails initialization. This is to make sure that execution path is covered. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-03-28 18:11:31 +01:00
# device_get_binding() compares pointers first before doing strcmp().
# However, enabling coverage forces -O0 to disable any compiler
# optimizations. There would be multiple copies of the same string,
docs: fix misspelling across the tree Found a few annoying typos and figured I better run script and fix anything it can find, here are the results... Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-06-18 20:45:40 +02:00
# and the code pathing doing pointer comparison would not be tested
tests/kernel/device: extends test for code coverage device_get_binding() compares pointers first before doing strcmp(). However, enabling coverage forces -O0 to disable any compiler optimizations. There would be multiple copies of the same string, and the code pathing doing pointer comparsion would not be tested at all. So add this flag to merge string constants such that the pointer comparison would be exercised. This also adds a bad driver which fails initialization. This is to make sure that execution path is covered. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2019-03-28 18:11:31 +01:00
# at all. So add this flag to merge string constants such that
# the pointer comparison would be exercised.
zephyr_cc_option_ifdef(CONFIG_COVERAGE -fmerge-constants)
Copy permalink