| commit | f5705dd1de91f3adf3f63ee232eae31b9bcf3901 | [log] [tgz] |
|---|---|---|
| author | Anthony DiGirolamo <tonymd@pigweed.infra.roller.google.com> | Thu Oct 24 16:31:12 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 24 16:31:12 2024 +0000 |
| tree | da28386960544af776fcd7e8b15a70a99b88b37f | |
| parent | 25c8d3e3fbd21fea0e9fff35a275f0148c2c0787 [diff] |
roll: pigweed pw_build: Fix default build targets for watch and project_builder
Restores 'out' as the default build directory.
Restores passing in only target names with no build directory
specified via -C.
The default build command to run when unspecified on the command line
is now:
1. When running pw watch or project_builder under bazel assume the
build commands to run are 'bazel build' followed by 'bazel test'.
2. When running outside bazel assume the build command is ninja
3. Can be overriden with --default-build-system {ninja,bazel}
Bugfix for file naming on separate log files per out directory. E.g.
pw watch -C out/gn docs \
-C out/bazel //... \
--build-system-command out/bazel 'bazel build' \
--build-system-command out/bazel 'bazel test' \
--logfile out/build.txt --separate-logfiles
Creates the following logfiles:
out/bazel -> out/build_out_bazel.txt
out/gn -> out/build_out_gn.txt
global -> out/build.txt
Original-Bug: 360140397
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/244254
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: 1668d6cae6310a41028307588761aecb55b3dc14
Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: ae426510b588dc..1668d6cae6310a
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8733180313548662433
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I406bc3f59a3e40bb8452b37e0bcdadc9c453d555
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/244372
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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.