michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/tests/bluetooth/ll_settings/CMakeLists.txt

11 lines
326 B
CMake
Raw Permalink Normal View History

tests: Bluetooth: Add test case for settings in the controller. Test case to set and change Company Id and Subversion Number. Signed-off-by: Wolfgang Puffitsch <wopu@demant.com>
2019-07-18 12:31:19 +02:00
# SPDX-License-Identifier: Apache-2.0
cmake: increase minimal required version to 3.20.0 Move to CMake 3.20.0. At the Toolchain WG it was decided to move to CMake 3.20.0. The main reason for increasing CMake version is better toolchain support. Better toolchain support is added in the following CMake versions: - armclang, CMake 3.15 - Intel oneAPI, CMake 3.20 - IAR, CMake 3.15 and 3.20 Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-08-10 14:44:56 +02:00
cmake_minimum_required(VERSION 3.20.0)
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 02:58:50 +02:00
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
tests: Bluetooth: Add test case for settings in the controller. Test case to set and change Company Id and Subversion Number. Signed-off-by: Wolfgang Puffitsch <wopu@demant.com>
2019-07-18 12:31:19 +02:00
project(bluetooth_ll_settings)
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-02-12 15:00:46 +01:00
zephyr_library_include_directories(${ZEPHYR_BASE}/subsys/bluetooth/controller/include)
tests: Bluetooth: Add test case for settings in the controller. Test case to set and change Company Id and Subversion Number. Signed-off-by: Wolfgang Puffitsch <wopu@demant.com>
2019-07-18 12:31:19 +02:00
FILE(GLOB app_sources src/*.c)
target_sources(app PRIVATE ${app_sources})
Copy permalink