Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 084394795a308f007a4c1655b1e0e779a10ae2d0
commit084394795a308f007a4c1655b1e0e779a10ae2d0[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Apr 10 18:44:41 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 10 18:44:41 2024 +0000
treed5652ec7a3d6bb0ff6698db3f7f9f768382273ee
parent6f1bdfb9891bc2cb8a8badcb5435444ed0df58d2 [diff]
[third_party/pigweed] Roll 2 commits

e1fa7dc22ad709d pw_build: Disable C23 extension warnings
e16b817993ed36d pw_{cli,presubmit}: Move ToolRunner

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: d578e9425943c63..e1fa7dc22ad709d
Roller-URL: https://ci.chromium.org/b/8751019441124398833
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I39e00067a1a14378059e85e821579b9ffb667079
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/202872
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: d5652ec7a3d6bb0ff6698db3f7f9f768382273ee
  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!