| commit | fe0d1b2705253c420c89154628f72185e8d93ee5 | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Wed Oct 02 17:24:27 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 02 17:24:27 2024 +0000 |
| tree | 82380463fb9884fcb84b911044c68c65234c6fd3 | |
| parent | a53ceb84f4670182c3d65b960edc08b93e4c1e12 [diff] |
roll: pigweed pw_chrono: Properly stamp build time in Bazel Before this change, the generated build_time.h header would be unconditionally cached between builds. This means the time in build_time.h would reflect not the actual time when the build command was run, but the time when the cached version of the file was built, which could have been in the distant past. After this change the caching behavior depends on how Bazel is invoked: 1. By default, the file is cached as before. 2. If Bazel is invoked with the --stamp flag, the file will be rebuilt. This option should be used for release builds. Fixes: 367739962 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/237809 Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Original-Revision: 279ab4a35543900b62e674d14c2e663532ad5a18 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 974dd9e7201646..279ab4a3554390 Roller-URL: https://ci.chromium.org/b/8735170122760915649 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I154208a2db9e88b4f84e51fb0ab526b984143fb8 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/239315 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.