Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 618b3297c838c0ee7fc9f0dc6ae279da7f8dc3a1
commit618b3297c838c0ee7fc9f0dc6ae279da7f8dc3a1[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Mar 30 21:34:52 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Mar 30 21:34:52 2024 +0000
treeb3993a8917f74b8e38472afdd0a668d967eaa67a
parentf8d6b530844da0b87faa1835dc42da12df30e6e8 [diff]
[roll third_party/pigweed] roll: cmake

From: version:2@3.28.3.chromium.8
To: version:2@3.29.0.chromium.8
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/200943
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: a63e2f7eb487832..d7c9aedb4ba94e1
Roller-URL: https://ci.chromium.org/b/8752005233189285745
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I7ee6663d33cf9c549ad6eae766abc44a3448dc7f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201191
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: b3993a8917f74b8e38472afdd0a668d967eaa67a
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!