Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1b4eee8ec362a23ee5a66000ad323b7a38632d56
commit1b4eee8ec362a23ee5a66000ad323b7a38632d56[log] [tgz]
authorDave Roth <davidroth@pigweed.infra.roller.google.com>Thu Sep 19 00:02:46 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Sep 19 00:02:46 2024 +0000
tree5d5974d7e97154db4909fbe0ff4254745c1c021e
parentb802c751db013a94ecd0552971350ee4f97a92f5 [diff]
roll: pigweed pw_build: Ensure PythonPackages dir tree exists

When building the PythonPackages directory tree, the parent tree
may not always exist, for example if it wasn't created by stamp files.

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

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 7f4759a3877ac3..c1c7dac7e1e66d
Roller-URL: https://ci.chromium.org/b/8736413381346356401
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1866b4d8838d7e1200ea8c60fbdf9ba8db9f1050
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/236759
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 5d5974d7e97154db4909fbe0ff4254745c1c021e
  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.