| commit | b3c932ece76a0b81c5e9ade26fd78140ca9f68b7 | [log] [tgz] |
|---|---|---|
| author | Anthony DiGirolamo <tonymd@pigweed.infra.roller.google.com> | Mon Oct 07 23:00:15 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 07 23:00:15 2024 +0000 |
| tree | 3635ad2301e1c768eae7cb639e0179b67090a69c | |
| parent | 3ad2c3c4d9763505f53ada7b1c57cff713d3e1c5 [diff] |
roll: pigweed pw_build: Fix pw_python_venv generated requirements pw_python_venv was always adding the //pw_build/py gn target to the list of dependencies to base the generated requirements on. This is usually not an issue if pw_build is included. However if it isn't needed extra 3p deps were always getting added from pw_build regardless. For example if a venv only needed //pw_docgen/py and //pw_status/py the generated_requirements would include all these extra packages due to pw_build being added in along with all their 3p deps: //pw_arduino_build/py:py //pw_build/py:py //pw_cli/py:py //pw_config_loader/py:py //pw_docgen/py:py //pw_env_setup/py:py //pw_package/py:py //pw_presubmit/py:py //pw_status/py:py //pw_stm32cube_build/py:py This change fixes it so only these two are added: //pw_docgen/py:py //pw_status/py:py Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/240792 Original-Revision: 87f43fec003b4befd74b2362962a76dff7105253 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 29fc404197899d..87f43fec003b4b Roller-URL: https://ci.chromium.org/b/8734696769903185649 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I9d8eab39568f67a90e7853c2c658c3e6956726da Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/240619 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>
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.
git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart cd pw_bazel_quickstart
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.
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
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
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)
bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.
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.
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.