Google Git
Sign in
pigweed / pigweed / quickstart / bazel / fbe8b9647da5174c9ca84820edebe14d75b20632
commitfbe8b9647da5174c9ca84820edebe14d75b20632[log] [tgz]
authorArmando Montanez <amontanez@pigweed.infra.roller.google.com>Mon Oct 21 22:57:49 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Oct 21 22:57:49 2024 +0000
treee20023b13c1ba595ba222ab2dd1def19fbf94df6
parente522939523af35cb6223cd00a61cb84667d36649 [diff]
roll: pigweed pw_log_tokenized: Only rely on headers for tokenized_args_test

In the Bazel build, instead of depending directly on the
pw_log_tokenized backend, just depend on pw_log and the header target to
try to prevent issues where a conflicting backend is pulled in.

Original-Bug: b/374815972
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/243732
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: dff651106a656dbf41b21facfc4c6734af46db48

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 5e7d1a0fddab12..dff651106a656d
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8733427817589890449
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I670a8628881b946707b3ced3105a9865862d193f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/243634
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>
1 file changed
tree: e20023b13c1ba595ba222ab2dd1def19fbf94df6
  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. .clangd.shared
  14. .gitignore
  15. .pw_console.yaml
  16. AUTHORS
  17. BUILD.bazel
  18. CONTRIBUTING.md
  19. LICENSE
  20. MODULE.bazel
  21. OWNERS
  22. pigweed.json
  23. README.md
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.