Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1a1c20623048fbed2afe4f153c099d61ab514051
commit1a1c20623048fbed2afe4f153c099d61ab514051[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu May 16 07:13:32 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 16 07:13:32 2024 +0000
treecb8a21ac50a3eb4157ec604f4ce993e43d639a1e
parent3aaa18d1f2f174acae71c4923b7628550d9a0b29 [diff]
[roll third_party/pigweed] pw_proto: Create genrule for raw rpc with prefix

Original-Bug: 340749161
Test: Code on android main uses it and can build.
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209992
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 843bd1cf3b198a4..6393be463cc0815
Roller-URL: https://ci.chromium.org/b/8747801384410543537
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I389fe1e53aff4b111c05085395db335c5b54585c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210133
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: cb8a21ac50a3eb4157ec604f4ce993e43d639a1e
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

git clone --recursive https://pigweed.googlesource.com/pigweed/quickstart/bazel

If you already cloned but forgot to include --recursive, run git submodule update --init to pull all submodules.

TODO: b/300695111 - Don't require submodules for this example.

Building

We‘ll assume you already have Bazel on your system. If you don’t, the recommended way to get it is through Bazelisk.

To build the entire project (including building the application for both the host and the STM32 Discovery Board), run

bazel build //...

To run the application locally on your machine, run,

bazel run //src:echo

Flashing

To flash the firmware to a STM32F429 Discovery Board connected to your machine, run,

bazel run //tools:flash

Note that you don't need to build the firmware first: Bazel knows that the firmware images are needed to flash the board, and will build them for you. And if you edit the source of the firmware or any of its dependencies, it will get rebuilt when you flash.

Communicating

Run,

bazel run //tools:miniterm -- /dev/ttyACM0 --filter=debug

to communicate with the board. When you transmit a character, you should get the same character back!