-s/--source is a legacy option. There's a proposal to actually use it
for something else in Zephyr now:
https://github.com/zephyrproject-rtos/zephyr/pull/40669
Let's update README.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Zephyr includes are now prefixed with <zephyr/...>. While the old path
can still be used when CONFIG_LEGACY_INCLUDE_PATH=y, it's better to be
prepared for the future.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Fixes: #39270
The latest zephyrprojectrtos/ci no longer sets ZEPHYR_SDK_INSTALL_DIR
in the environment and doesn't register the Zephyr-SDK as a CMake
package in the CMake package registry.
To ensure the the Zephyr SDK can be correctly discovered by
find_package(Zephyr-sdk) we add `/opt/toolchains` to the
CMAKE_PREFIX_PATH environment variable which is a list containing
additional search prefixes for the `find_package()` function.
Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
The initial idea behind this code was to showcase documentation. It does
not add any special value to the sample, so remove it. A proper library
can be added in the future.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Use the recently introduced GPIO API that allows obtaining pin state
using the gpio_dt_spec struct.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Provide an overlay to shows how to run the example-application on boards
that are part of the Zephyr tree. Sometimes initial development is
performed on dev-kits, so it can be useful. A different vendor than the
one used for the custom board (Nordic) has been chosen to show
application portability.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>