[third_party/pigweed] Roll 5 commits

006ab828252ebef pw_ide: Support including and/or excluding targets
54365f77ab968de pw_presubmit: Refactor Python Black formatter supp
f3efc84d58d607a pw_presubmit: Refactor Bazel formatter support
7ad13e08167f560 pw_bluetooth: Add example of using to_underlying
d05115caa2f47db pw_build: ProjectBuilder documentation

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 0ee6ca26f6a11aa..006ab828252ebef
Roller-URL: https://ci.chromium.org/b/8752175199599889713
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I03603c5808622dedecf003617bedca8c43018b37
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200932
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: 705636e169609930acc8d2275464534269a1baba
  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!