Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 6069fa19ca0fddffba31d7b8bb29c09fc2e4cd0a
commit6069fa19ca0fddffba31d7b8bb29c09fc2e4cd0a[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 09 00:42:48 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 09 00:42:48 2024 +0000
treece2e8c5953ac6197ee57ea28fe41de5021a8452d
parent079232b34f48dfc282e7fa540977e8fe154f5449 [diff]
[third_party/pigweed] Roll 2 commits

5c8c8074339c641 pw_build_android: Make Common Backends static
bff185f46d3332f pw_async2: Add PendableAsTask

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 4c1a7158b663f11..5c8c8074339c641
Roller-URL: https://ci.chromium.org/b/8751178061908100273
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic7e22f5829cc59b06b7bf7d30ad8869733f8a4c6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/202650
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: ce2e8c5953ac6197ee57ea28fe41de5021a8452d
  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!