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 | ||
| README.rst | ||
| prj.conf | ||
| sample.yaml | ||
README.rst
.. _microbit_display: BBC micro:bit display ##################### Overview ******** A simple example that demonstrates how to use the 5x5 LED matrix display on the BBC micro:bit board. Building ******** This project outputs various things on the BBC micro:bit display. It can be built as follows: .. zephyr-app-commands:: :zephyr-app: samples/boards/bbc_microbit/display :board: bbc_microbit :goals: build :compact: Sample Output ============= The sample app displays a countdown of the characters 9-0, iterates through all pixels one-by-one, displays a smiley face, some animations, and finally the text "Hello Zephyr!" by scrolling.