| commit | f6296b5d344eb6e1edda18358670bcc69b43abd0 | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Fri Jun 28 22:39:42 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 28 22:39:42 2024 +0000 |
| tree | 10e42b6b3323666721d835ae2c6cffb7f5d4bf0e | |
| parent | 3371a5753d3dcc9c82af04f399418856915c603f [diff] |
roll: pigweed, pw_toolchain: bazel: Add back to CI some building targets These targets all build now and no longer need to be tagged manual. Original-Bug: 261603269 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218698 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: d36dcb9fedb7b88..e12c9358911b3b2 Roller-URL: https://ci.chromium.org/b/8743849625224279041 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I299a63c71bdeb26d2b51d76dee95395e6f8963a2 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218801 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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!