| commit | 5d81f79cddb71222a5d978ed70af0f05d6821b26 | [log] [tgz] |
|---|---|---|
| author | Alexei Frolov <frolv@pigweed.infra.roller.google.com> | Tue Oct 22 21:10:04 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 22 21:10:04 2024 +0000 |
| tree | 1e5d60f1d57ee45ab8b42ffec50d48b5250c22b9 | |
| parent | 654368193363960f63eda1b9f36f9bebe5537872 [diff] |
roll: pigweed pw_protobuf: Allow .pwpb_options as an options file extension pw_protobuf allows providing code generator options through a separate options file. These files are typically found automatically by the compiler by scanning the source proto directory for a file matching the name of an input proto file with an options file extension. Previously, the only supported options extension was `.options`. This was inspired by Nanopb. However, this results in conflicts with Nanopb in projects which use it alongside pw_protobuf (such as Pigweed itself). This change adds `.pwpb_options` as the primary options file extension for pw_protobuf. `.options` is still supported by default, but a code generator flag is offered to disable it for projects choosing to strictly separate Nanopb and pw_protobuf options. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/241137 Original-Revision: 9525d75843cede1c67f78de7c2f86bb30ac98efe Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 19ba505b67fd82..9525d75843cede Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8733344011463426113 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Id0f1b55690f3fea8372f7adabbd618155797a523 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/243934 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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.