Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 44968877b765054803357282246ba0f2b3a67f86
commit44968877b765054803357282246ba0f2b3a67f86[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 23 18:55:10 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 23 18:55:10 2024 +0000
treeae0f530564e44f89fb620716577ff19eada7e76e
parentb03a89c04fc59da380c3ecd107916565f372b965 [diff]
[third_party/pigweed] Roll 3 commits

d01aa29f9f9e113 pw_presubmit: Allow disabling hook creation
bc6388fd60ff21b pw_tokenizer: Switch detokenize.h docs to Doxygen
5ee9af02a1ef96c docs: Mention @deprecated in the Doxygen style gui

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: c6e83c173d13b52..d01aa29f9f9e113
Roller-URL: https://ci.chromium.org/b/8749840977003014321
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ia96c67372284d67fbbb41ea5411b455a9922892a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205971
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: ae0f530564e44f89fb620716577ff19eada7e76e
  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!