Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d196e429f3570069e72c4c54881a1b3cb0cf05b1
commitd196e429f3570069e72c4c54881a1b3cb0cf05b1[log] [tgz]
authorAlexei Frolov <frolv@pigweed.infra.roller.google.com>Mon Oct 14 21:07:32 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Oct 14 21:07:32 2024 +0000
tree1fd8e53afa3669aa1e2927adbbb8e7853c1af062
parent7f215741964eaec345680b35ad3e470b9b0eed0f [diff]
roll: pigweed pw_protobuf: Force use of callbacks for oneof

pw_protobuf's message structures previously generated each of the
members of a oneof group as a separate struct member, allowing multiple
of them to be set to serialize semantically-invalid wire messages.

This replaces oneof struct member generation with a single callback for
the entire oneof group, allowing the user to encode/decode the desired
oneof field using the wire stream encoder and decoder.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/236592
Original-Revision: 53d4032b027055342c7321bef95e8a23e805c74c

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 064c7681ce438b..53d4032b027055
Roll-Count: 1
Roller-URL: https://ci.chromium.org/b/8734069274188882865
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I12b0beac1f48328a98895193400e83b9fe3ef683
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/242075
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: 1fd8e53afa3669aa1e2927adbbb8e7853c1af062
  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.