OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/kernel/device/CMakeLists.txt

17 lines
651 B
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
cmake: increase minimal required version to 3.13.1 Move to latest cmake version with many bug fixes and enhancements. Signed-off-by: Anas Nashif <anas.nashif@intel.com> Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-12-11 23:33:23 +08:00
cmake_minimum_required(VERSION 3.13.1)
cmake: use find_package to locate Zephyr Using find_package to locate Zephyr. Old behavior was to use $ENV{ZEPHYR_BASE} for inclusion of boiler plate code. Whenever an automatic run of CMake happend by the build system / IDE then it was required that ZEPHYR_BASE was defined. Using ZEPHYR_BASE only to locate the Zephyr package allows CMake to cache the base variable and thus allowing subsequent invocation even if ZEPHYR_BASE is not set in the environment. It also removes the risk of strange build results if a user switchs between different Zephyr based project folders and forgetting to reset ZEPHYR_BASE before running ninja / make. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-02-12 22:00:46 +08:00
find_package(Zephyr 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 22:54:09 +08: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 12:36:01 +08: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-29 01:11:31 +08: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-19 02:45:40 +08: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-29 01:11:31 +08: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)