zephyr/tests/subsys
Torsten Rasmussen 407b49b35c 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-03-27 16:23:46 +01:00
..
canbus cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
dfu cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
fs cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
jwt cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
logging cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
settings cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
shell/shell_history cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
storage/flash_map cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
tracing cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
usb cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00