roll: pigweed pw_third_party: Fix pw_third_party.nanopb for Zephyr builds pw_third_party.nanopb currently points to native CMake targets defined by nanopb. These targets are not configured to use build flags provided by Zephyr. In Zephyr builds, users should instead use the nanopb Zephyr module, which builds nanopb in a Zephyr-aware manner and exposes it via the `zephyr_interface` interface target. Thus, for Zephyr builds, pw_third_party.nanopb should point to zephyr_interface to correctly expose nanopb. Test: Successfully built a Zephyr project that included CMake targets that use nanopb via the pw_third_party.nanopb target. Previously, this resulted in nanopb being compiled without the correct target flags. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/344312 Copybara-Verified: Copybara Prod <copybara-worker-blackhole@google.com> Original-Revision: 3f6acafe2f5bd523469d7916904db50259f2eb3d Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: fc4c2303b05c9b..3f6acafe2f5bd5 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8697894333994396833 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I9900dafff5008624faf35951d49ce0d9508993c2 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/345832 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It is a LED-blinking service (featuring RPC control!) for the Raspberry Pi Pico. It can also be run on any computer using the included simulator.
git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart cd pw_bazel_quickstart
The only dependency that must be installed is Bazelisk.
Bazelisk is a launcher for the Bazel build system that allows for easy management of multiple Bazel versions.
Instructions for installing Bazelisk can be found here.
To run the simulator, type: bazelisk run //apps/blinky:simulator_blinky Then, in a new console, connect to the simulator using: bazelisk run //apps/blinky:simulator_console
To start, connect a Raspberry Pi Pico, Pico 2, or debug probe via USB.
To run on the Raspberry Pi Pico, type: bazelisk run //apps/blinky:flash_rp2040 Then, in a new console, connect to the device using: bazelisk run //apps/blinky:rp2040_console
Once connected with a console, RPCs can be sent to control the LED. Try running:
device.set_led(True) device.set_led(False) device.toggle_led() device.blink(blink_count=3)
bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.
bazelisk run @pigweed//targets/rp2040/py:unit_test_server in one console followed by bazelisk test //... --config=rp2040 will also allow running the unit tests on-device.
Try poking around the codebase for inspiration about how Pigweed projects can be organized. Most of the relevant code in this quickstart (including RPC definitions) is inside modules/blinky, with some client-side Python code in tools/console.py.