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>
18 lines
690 B
CMake
18 lines
690 B
CMake
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
cmake_minimum_required(VERSION 3.13.1)
|
|
find_package(Zephyr HINTS $ENV{ZEPHYR_BASE})
|
|
project(fp_sharing)
|
|
|
|
# Some boards are significantly slower than others resulting in the test
|
|
# output being in the range of every few seconds to every few minutes. To
|
|
# compensate for this, one can control the number of iterations in the PI
|
|
# calculation through PI_NUM_ITERATIONS. Lowering this value will increase
|
|
# the speed of the test but it will come at the expense of precision.
|
|
|
|
set_ifndef(PI_NUM_ITERATIONS 700000)
|
|
zephyr_compile_definitions(PI_NUM_ITERATIONS=${PI_NUM_ITERATIONS})
|
|
|
|
FILE(GLOB app_sources src/*.c)
|
|
target_sources(app PRIVATE ${app_sources})
|