zephyr/tests/bluetooth/init
Marc Herbert debade9121 tests: make find_package(Zephyr...) REQUIRED
... because it is (required).

This makes a difference when building with CMake and forgetting
ZEPHYR_BASE or not registering Zephyr in the CMake package registry.

In this particular case, REQUIRED turns this harmless looking log
statement:

-- Could NOT find Zephyr (missing: Zephyr_DIR)
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- ...
-- ...
-- ...
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:8 (target_sources):
  Cannot specify sources for target "app" which is not built by
  this project.

... into this louder, clearer, faster and (last but not least) final
error:

CMake Error at CMakeLists.txt:5 (find_package):
  Could not find a package configuration file provided by "Zephyr" with
  any of the following names:

    ZephyrConfig.cmake
    zephyr-config.cmake

  Add the installation prefix of "Zephyr" to CMAKE_PREFIX_PATH or set
  "Zephyr_DIR" to a directory containing one of the above files.  If
  "Zephyr" provides a separate development package or SDK, be sure it
  has been installed.

-- Configuring incomplete, errors occurred!

Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-05-29 10:47:25 +02:00
..
src cleanup: include/: move misc/printk.h to sys/printk.h 2019-06-27 22:55:49 -04:00
CMakeLists.txt tests: make find_package(Zephyr...) REQUIRED 2020-05-29 10:47:25 +02:00
prj.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_0.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_1.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_2.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_3.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_4.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_5.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_6.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_7.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_8.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_9.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_10.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_11.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_12.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_13.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_14.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_15.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_16.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_17.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_18.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_19.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_20.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_21.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_22.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_controller_4_0_ll_sw_split.conf Bluetooth: controller: Enable additional ULL/LLL CI tests 2019-05-06 14:41:58 +02:00
prj_controller_dbg_ll_sw_split.conf Bluetooth: controller: Enable additional ULL/LLL CI tests 2019-05-06 14:41:58 +02:00
prj_controller_ll_sw_split.conf Bluetooth: controller: Enable additional ULL/LLL CI tests 2019-05-06 14:41:58 +02:00
prj_controller_tiny_ll_sw_split.conf Bluetooth: controller: Enable additional ULL/LLL CI tests 2019-05-06 14:41:58 +02:00
prj_h5.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
prj_h5_dbg.conf tests: init: use ztest APIs 2017-09-13 09:48:34 -04:00
testcase.yaml Bluetooth: controller: Remove legacy LL 2020-05-08 15:07:00 +02:00