zephyr/drivers/bluetooth/CMakeLists.txt

# SPDX-License-Identifier: Apache-2.0

zephyr_library()
zephyr_library_property(ALLOW_EMPTY TRUE)
zephyr_library_include_directories(${ZEPHYR_BASE}/subsys/bluetooth)
add_subdirectory(hci)
license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-04-06 21:08:09 +08:00			`# SPDX-License-Identifier: Apache-2.0`

drivers: bluetooth: build as static library Instead of putting object files inside libzephyr.a, simply build a separate static library as most other driver types are doing this already. Note that the include to subsys/bluetooth has been moved from under drivers/bluetooth to subsys/bluetooth, as it is actually the subsystem's job to make sure the include directories are correct. Signed-off-by: Daniel Leung <daniel.leung@intel.com> 2021-08-05 05:22:54 +08:00			`zephyr_library()`
Bluetooth: Move crypto toolbox functions from `smp.c` to their own files Move functions defined in the Cryptographic toolbox of the Bluetooth specification inside their own files in the following folder: `zephyr/subsys/bluetooth/bt_crypto`. The functions were previously implemented in `zephyr/subsys/bluetooth/host/smp.c`. The cryptographic toolbox functions can now be accessed from outside of the host. In addition to that, tests for each cryptographic toolbox functions have been added. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no> 2022-10-31 21:58:02 +08:00			`zephyr_library_property(ALLOW_EMPTY TRUE)`
drivers: bluetooth: build as static library Instead of putting object files inside libzephyr.a, simply build a separate static library as most other driver types are doing this already. Note that the include to subsys/bluetooth has been moved from under drivers/bluetooth to subsys/bluetooth, as it is actually the subsystem's job to make sure the include directories are correct. Signed-off-by: Daniel Leung <daniel.leung@intel.com> 2021-08-05 05:22:54 +08:00			`zephyr_library_include_directories(${ZEPHYR_BASE}/subsys/bluetooth)`
Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no> 2017-10-27 21:43:34 +08:00			`add_subdirectory(hci)`