zephyr/tests/bluetooth/init
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
..
src
CMakeLists.txt
prj_1.conf
prj_2.conf
prj_3.conf
prj_4.conf
prj_5.conf
prj_6.conf
prj_7.conf
prj_8.conf
prj_9.conf
prj_10.conf
prj_11.conf
prj_12.conf
prj_13.conf
prj_14.conf
prj_15.conf
prj_16.conf
prj_17.conf
prj_18.conf
prj_19.conf
prj_20.conf
prj_21.conf
prj_22.conf
prj_0.conf
prj_controller_4_0_ll_sw_split.conf
prj_controller_4_0.conf
prj_controller_dbg_ll_sw_split.conf
prj_controller_dbg.conf
prj_controller_ll_sw_split.conf
prj_controller_tiny_ll_sw_split.conf
prj_controller_tiny.conf
prj_controller.conf
prj_h5_dbg.conf
prj_h5.conf
prj.conf
testcase.yaml