Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 55c0fe9f58504998d59cc7165c56539963f7b978
commit55c0fe9f58504998d59cc7165c56539963f7b978[log] [tgz]
authorArmando Montanez <amontanez@pigweed.infra.roller.google.com>Wed Oct 01 00:35:57 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Oct 01 00:35:57 2025 -0700
tree235484055b70737e1f7beb69450b9ef6e28bfb9a
parentaf5eccff60cad56658903017b14bf11a3e4d0cf2 [diff]
roll: pigweed pw_ide: Rework compile commands database creation

Reworks the aspect-based compile commands generation to perform a
separate build to generate the compile commands database, using the
results of the BEP JSON file to determine which fragments were created.
This is significantly faster then the previous clean/generate/glob
approach.

Original-Fixed: b/446010661
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/325493
Original-Revision: 5a327fbe4d02eab862afa970e7eaeaf306fb7d34

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 6fef9caa5d75d9..5a327fbe4d02ea
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8702229844429616817
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ibd247a1c485c8341970a82df192d115bdc42247f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/327534
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>
1 file changed
tree: 235484055b70737e1f7beb69450b9ef6e28bfb9a
  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.