| commit | 2b1d686b74895a38b65ca6e243488bd25177f277 | [log] [tgz] |
|---|---|---|
| author | Carlos Chinchilla <cachinchilla@pigweed.infra.roller.google.com> | Mon Jul 22 18:23:35 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 22 18:23:35 2024 +0000 |
| tree | 3c558eb6fc47caeb0bd3d0794781851aa0e05a4f | |
| parent | 15880bc90b0152c427c8e711a563e776a3b8f005 [diff] |
roll: pigweed, pw_toolchain: pw_rpc: Build proto path arg list for Soong For every .proto file in the Soong genrule to build a nanopb proto, add its parent's parent's directory as a --proto-path argument to the protobuf compiler. This allows genrules to have protos from different sources. The requirement is that all sources to the same genrule are prefixed once. Test: Compiled prefixed proto with prefixed dependencies. Passes presubmits in Android main. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/225031 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: dd2720f7c2a5222..74bc3cad816843c Roller-URL: https://ci.chromium.org/b/8741689221048558129 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Icd3ad2ae0de3389a687f0367223537caac7bfc37 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225351 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>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
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.
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
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.
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!