zephyr/tests/bluetooth/mesh
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 cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
dbg.conf
friend.conf
gatt.conf
lpn.conf
microbit.conf Bluetooth: Mesh: Slab based segmentation handling 2020-03-19 15:54:26 +02:00
microbit_gatt.conf Bluetooth: Mesh: Slab based segmentation handling 2020-03-19 15:54:26 +02:00
nrf51-16k.conf Bluetooth: Mesh: Slab based segmentation handling 2020-03-19 15:54:26 +02:00
pb_gatt.conf
prj.conf
proxy.conf
testcase.yaml boards: nrf52840_pca10056: Rename board to nrf52840dk_nrf52840 2020-03-27 09:14:08 +01:00