Google GitGoogle Git
Sign in
pigweed/pigweed/quickstart/bazel/e2eb3caf7945ea40a64549660f45c94e96b74cf6
commit
e2eb3caf7945ea40a64549660f45c94e96b74cf6
[log]
author
Austin Foxley <afoxley@pigweed.infra.roller.google.com>
Sat Sep 26 01:53:51 2026 -0700
committer
CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Sat Sep 26 01:53:51 2026 -0700
tree
24545283b5ed45146b32cb6d4ccf106572ab1e33
parent
3b47b86a33655af8071dbc6940f99ce671a9ee7e [diff]
roll: pigweed pw_build: Fix bazel spurious repo resolution issue

Using build on --incompatible_enable_proto_toolchain_resolution instead
of common will invalidate various caches if another type of command is
run (like test, mod, run, etc...). This option is supported by all
command types so we can change to common.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/486649
Original-Revision: 4184cfb1e80c38e4f1d2ee3fb21d7b6b337723c7

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 43f38fa5c0a0c5..4184cfb1e80c38
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8669610067538089665
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ife053b6545591467daa5c4ca6dc6d76f648233e7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/486729
1 file changed
tree: 24545283b5ed45146b32cb6d4ccf106572ab1e33
  1. .github/
  2. .vscode/
  3. apps/
  4. modules/
  5. system/
  6. targets/
  7. tools/
  8. .bazelignore
  9. .bazelrc
  10. .bazelversion
  11. .buildifier.json
  12. .clang-format
  13. .clang-tidy
  14. .clangd.shared
  15. .gitignore
  16. .pw_console.yaml
  17. .pylintrc
  18. AUTHORS
  19. BUILD.bazel
  20. CONTRIBUTING.md
  21. LICENSE
  22. MODULE.bazel
  23. MODULE.bazel.lock
  24. mypy.ini
  25. OWNERS
  26. pw
  27. README.md
  28. workflows.json
README.md

Pigweed: minimal Bazel example

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.

Getting the code

git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart
cd pw_bazel_quickstart

Dependencies

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.

Running on the simulator

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

Running on hardware

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

Controlling the LED

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)

Running unit tests on the host device

bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.

Running unit tests on hardware

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.

Next steps

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.