roll: pigweed Revert "pw_build: Fix build spew for pw_copy_and_patch_file"

This reverts commit b8f9f5688ba6a79fc224864c21d0a38214b086df.

Reason for revert: temporarily revert until patch available in internal repo.

Original change's description:
> pw_build: Fix build spew for pw_copy_and_patch_file
>
> Increases log level to filter out unnecessary INFO level logs.
>
> Original-Bug: b/370775215
> Change-Id: Ib94c09279165a322b1db425396ba44155810d7c2
> Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/239132
> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
> Reviewed-by: Dave Roth <davidroth@google.com>
> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
> Docs-Not-Needed: Armando Montanez <amontanez@google.com>
> Pigweed-Auto-Submit: Armando Montanez <amontanez@google.com>
> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com>

TBR=amontanez@google.com,pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com,android-build-ayeaye@system.gserviceaccount.com,davidroth@google.com,auto-submit@pigweed-service-accounts.iam.gserviceaccount.com

Original-Bug: b/370775215
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/239354
Original-Revision: 974dd9e72016464ee28f2831086ea6f561257939

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