Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 122681a3508a40fef0d192462e0742f28e59654e
commit122681a3508a40fef0d192462e0742f28e59654e[log] [tgz]
authorJiacheng Lu <lujc@pigweed.infra.roller.google.com>Thu Jun 06 09:15:41 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 06 09:15:41 2024 +0000
tree48919f5d677f753bd63e406a3559bd8f87838a7d
parent2e1a74c47faedb46e6790f3cd1a581172bdb90e7 [diff]
[third_party/pigweed] Roll 2 commits

243ba33cd5434c7 pw_multisink: Add GetUnreadEntriesSize to Drain
4885f584c9a27aa pw_ring_buffer: Add EntriesSize API to Reader

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: da7ee077f24a9bb..243ba33cd5434c7
Roller-URL: https://ci.chromium.org/b/8745891215313931713
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1640b4d2853f5048f83bbc30ce744d4ecbfd1562
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214197
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 48919f5d677f753bd63e406a3559bd8f87838a7d
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  13. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!