| commit | 95f14b4d5d75598e6d42a45847fe48ab41d71364 | [log] [tgz] |
|---|---|---|
| author | Austin Foxley <afoxley@pigweed.infra.roller.google.com> | Wed Oct 09 18:35:43 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 09 18:35:43 2024 +0000 |
| tree | 98637023c00143827ec65fb93de9374384bb45c7 | |
| parent | af067c3362620ac12fd957d093b5d8553257da82 [diff] |
roll: pigweed pw_protobuf: Support directly specifying options file locations Replace the existing import-prefix arg to pwpb protoc plugin with an option to directly specify the location of any .options files to load from. The import-prefix option was added to try and find options files whose proto paths had been modified via the import_prefix bazel attr. This worked fine as long as you were careful to place your options files in a place where the existing search paths could find them. We've found it's easy to break this arrangement if the real path of the .options file isn't prefixed by the virtual import path of the proto. This could be fixed by a further complicated dance of constructing search paths that the plugin will then further mangle to check if the options file exists. This CL instead directly specifies the location of any options files for the pwpb plugin, while leaving in place the existing search path logic required for nanopb options files. Original-Bug: https://pwbug.dev/253068333 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/240833 Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Original-Revision: 6efc99b3ee854dd54a0b1465d9014c54e01b21b9 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 4321a46654fae2..6efc99b3ee854d Roller-URL: https://ci.chromium.org/b/8734531451229149041 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I30dd33dd6d0f7d667b29568f4ce18f2d7d0ab858 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/241043 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.