roll: pigweed changelog: Remove caching logic The cache invalidation logic is error-prone (who would have guessed!) and makes the code harder to read. Changelog automation users will now need to run the script from start to end. If it fails or gets interrupted, they'll have to start over. Long-term we will make this less painful by parallelizing the automation as much as possible and making it resilient to all failure modes. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/348973 Original-Revision: 0d38b288172b26d0324abfe4fc525466c2d6dd1b Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: ed1729e4857485..0d38b288172b26 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8697167821255342257 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I70ed7766c52a95400a4f45bfc0e0051c11dae082 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/349152 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.