| commit | ea25c7d7eea62698186e01df39e935f510a01b0f | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Wed Jul 10 17:54:00 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 10 17:54:00 2024 +0000 |
| tree | 50ff99fbb4d1560f0e83bb5d1fb566e79effc850 | |
| parent | 35cfbfdef5439e66da743f4bb3bbad569cd39b87 [diff] |
roll: pigweed, pw_toolchain: bazel: Don't propagate flags to exec config This will improve cache hit rates, and also allow us to use @bazel_tool//tools/cpp:link_extra_libs for pw_assert and pw_log implementation targets (without these flags this does not work because you invariably end up with circular dependencies). Requires Bazel 8. Original-Bug: 234877642 Original-Bug: 315871648 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/220812 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 1d190f27e281304..1fc96205b72d872 Roller-URL: https://ci.chromium.org/b/8742778621249220449 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6a73bf3a6aa8da3831e843067d63da288e7eab6a Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/221292 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!