407b49b35c
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>
17 lines
651 B
CMake
17 lines
651 B
CMake
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
cmake_minimum_required(VERSION 3.13.1)
|
|
find_package(Zephyr HINTS $ENV{ZEPHYR_BASE})
|
|
project(device)
|
|
|
|
FILE(GLOB app_sources src/*.c)
|
|
target_sources(app PRIVATE ${app_sources})
|
|
|
|
# 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 comparison would not be tested
|
|
# 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)
|