| commit | 1d1d077fc3b349334bf9e30729f11d39e19d5ad2 | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Thu May 30 22:51:56 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 30 22:51:56 2024 +0000 |
| tree | a9cba7e394e95ff2ba9d6dd9948b677f1d31702c | |
| parent | 6c31d79162cfe1961c0766004dcfef31724207b8 [diff] |
[roll third_party/pigweed] pw_multisink: Fix compiler warnings for tests GCC warns about constructing a MultiBuf with an uninitialized array, so initialize it first. This isn't a problem in practice because the uninitialized data is never read. Also, ensure the test builds when joining is disabled, though none of the tests can run. Original-Bug: b/343480404 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/212051 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 694805ff7c3e249..272873750faa652 Roller-URL: https://ci.chromium.org/b/8746475709021352449 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Icc443dc3357a88bfd9bf0c15929b499893a31240 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/212416 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>
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!