| commit | 84398c6f6399775b95a9da2caec0366ad6429c67 | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Fri Jul 12 23:55:43 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 12 23:55:43 2024 +0000 |
| tree | 4a46fc6ca346c31f9cd6fe959a4ca01352751520 | |
| parent | 0176f6fbbc7822f4c242b3c3e5494ddb4e3ee1f6 [diff] |
roll: pigweed, pw_toolchain: pw_unit_test: Introduce googtest_platform This is intended as a workaround for https://github.com/bazelbuild/bazel/issues/23003 only, and will be deleted soon. Do not depend on any targets introduced in this CL from outside Pigweed! I verified that with this change and updates to `target_compatible_with`, http://pwrev.dev/221036 doesn't get any Bazel-level errors. (It still doesn't build, but the errors I get come from the C++ compiler, not Bazel---something about missing headers.) Original-Bug: 352808542 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/222812 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: e15bd2067e7a244..990ed9bb2f16bec Roller-URL: https://ci.chromium.org/b/8742574672140296577 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I531f21e6c3204955c91359c430c0ad49c124e1e0 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222643 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!