| commit | e4e6822993dbec8d60fa6cef8892fce1e0c0f31e | [log] [tgz] |
|---|---|---|
| author | Anthony DiGirolamo <tonymd@pigweed.infra.roller.google.com> | Thu May 16 22:20:29 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 16 22:20:29 2024 +0000 |
| tree | 43c375ce2563e4bcc5f411ace3e7801e2d7cf9df | |
| parent | f1d91f64ac3408053bcb741a78eab09810cc2bbd [diff] |
[roll third_party/pigweed] pw_build: pw_cc_test.lib fixup The bazel pw_cc_test rule was not removing the default test_main from the .lib subtarget. This prevents users from overriding due to multiple main functions being linked in. Also add a missing dep to //third_party/boringssl:build_test Original-Bug: 307825072, 341109859 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/210231 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: dcbe39839b38dd2..fe3b300897488d8 Roller-URL: https://ci.chromium.org/b/8747744732880490753 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I501f26bf2d18c549795f81235bd71c39986164d9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210208 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!