Google Git
Sign in
pigweed / pigweed / quickstart / bazel / db149f1ff3e9a863dff3c8f9cbfac1c3b0aa67b6
commitdb149f1ff3e9a863dff3c8f9cbfac1c3b0aa67b6[log] [tgz]
authorEric Rahm <erahm@pigweed.infra.roller.google.com>Sat Apr 27 03:57:42 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Apr 27 03:57:42 2024 +0000
treed7d13258cc06f2483cbbc9baee1c15a612d4e276
parent15960dc4cc0471b64aa5ea43315d8035e2dda2e6 [diff]
[roll third_party/pigweed] pw_unit_test: Add support for a test_main in CMake

Adds support to `pw_add_test` for a custom `test_main`. This is similar
to what we do for GN's `pw_test`.

Original-Fixes: 335865646

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/204872

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 188bd4726e0eca3..2d65e87e6086474
Roller-URL: https://ci.chromium.org/b/8749535042730970737
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I9793131238079d7d01017e95fca54b905e9029f7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206952
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: d7d13258cc06f2483cbbc9baee1c15a612d4e276
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

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.

Building

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

Flashing

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.

Communicating

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!