407b49b35c
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>
|
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| README.rst | ||
| rv32m1_vega_ri5cy.overlay | ||
| sample.yaml | ||
.. _ble_peripheral: Bluetooth: Peripheral ##################### Overview ******** Application demonstrating the BLE Peripheral role. It has several well-known and vendor-specific GATT services that it exposes. Requirements ************ * BlueZ running on the host, or * A board with BLE support Building and Running ******************** This sample can be found under :zephyr_file:`samples/bluetooth/peripheral` in the Zephyr tree. See :ref:`bluetooth samples section <bluetooth-samples>` for details.