Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1c02cc6b93f8843186235b48c6d53ac9c2d53d3d
commit1c02cc6b93f8843186235b48c6d53ac9c2d53d3d[log] [tgz]
authorAnthony DiGirolamo <tonymd@pigweed.infra.roller.google.com>Mon Sep 23 21:19:57 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Sep 23 21:19:57 2024 +0000
treef8c09ab6a71b7091b11ef9ffd85537d41c2e92c2
parentc21c0776c8e0219aede8da931d0420540d93f246 [diff]
roll: pigweed pw_docgen: Include required Python packages

This adds the missing beautifulsoup4, jsonschema and kconfiglib
packages to pw_docgen/py/setup.cfg. All are imported in pw_docgen code
and not upstream-only dependencies. Moved the pinned version numbers
out of pigweed_upstream_requirements.txt and into constraint.list.

Also remove pytz and psutil out of pigweed_upstream_requirements.txt,
they are in constraint.list already and not upstream-only packages.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/237334
Original-Revision: 751a5ae613ce227a70a53c40e2342dbd80a91951

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