Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 6330e29c08bc5ec8640bb8b997fd6a98311c770a
commit6330e29c08bc5ec8640bb8b997fd6a98311c770a[log] [tgz]
authorDarren Chan <chandarren@pigweed.infra.roller.google.com>Fri Oct 18 20:32:20 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Oct 18 20:32:20 2024 +0000
tree837ce300aefa96c37c4eb182eb0a941904fd54f9
parente22a8385dfb729ac1821673fa48b9fa98cfa0670 [diff]
roll: pigweed pw_bluetooth_sapphire: Add test config to bazelrc

Use --experimental_retain_test_configuration_across_testonly by default,
as otherwise the build config would differ for some test targets across
a testonly target boundary between the main build and aspect builds,
causing a conflicting action error.

Original-Bug: 374340793
Original-Fixed: 372017265
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/242452
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: 3e9c8837fbbc3b8105c6e1b77e7c14d4c1ad0d4e

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 170f745d98d101..3e9c8837fbbc3b
Roll-Count: 1
Roller-URL: https://ci.chromium.org/b/8733708772254706465
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1b8a07f7554de6edbbe87ce290d985fae36f48b3
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/243372
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: 837ce300aefa96c37c4eb182eb0a941904fd54f9
  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.