Create lib subsystem with empty Kconfig menu, subsystem build file.
Updated top-level build and documentation to include subsystem.
This was created to provide an example of how the `lib/` directory
can be connected to the Zephyr build system through `module.yml`,
and so that CI can verify that the extension settings used here
work with these sub-trees.
.
The approach follows the pattern of paralleling the Zephyr tree.
An empty subsystem was implemented rather than a non-empty one
in order to isolate the core changes from any specific library.
This provides a clean reference for users.
.
It was assumed that some users will want to strip out the `lib/`
subsystem separate from existing subsystems, and vice versa.
.
This was verified by:
- visually verifying a clean build of:
`west build -b custom_plank -p always example-application/app/`
- visually verifying the subsystem appeared in the correct
location in a clean build of:
`west build -b custom_plank -p always example-application/app/`
Signed-off-by: Gregory Shue <gregory.shue@legrand.us>
Add a working example for how to implement a west command within the
user's manifest repository. There is documentation for this, but we
should have some working code in here just to make life easier for
people.
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
With the recent changes in how Kconfig options are enabled using DT
helpers, using select leads to a better/more scalable pattern. Each
driver Kconfig option is expected to select its dependencies now.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
The option is no longer needed, zephyr,examplesensor driver will
automatically be selected based on DT (and because we enable all of its
dependencies, including CONFIG_SENSOR).
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Make zephyr,examplesensor driver option dependent on it being defined in
Kconfig and set its default based on DT status as well.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
Link to the relevant sections in the Zephyr documentation, including
application development and west topologies.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
-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>
