[third_party/pigweed] Roll 5 commits

3fbcf41574028ef docs: Revamp Doxygen style guide
19d58a7afb51ced pw_transfer: Implement adaptive windowing in C++
28826a8a3014f44 pw_{cli,presubmit}: Move git_repo to pw_cli
acc3de9c3173a4a pw_cli: Add Python deprecation decorator
003d721ee784560 pw_blob_store: Fix CMakeLists.txt pw_add_library()

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 57d41af75d9459d..3fbcf41574028ef
Roller-URL: https://ci.chromium.org/b/8750815492472729409
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I329f02d525414c4b08f98d10818740e96f21dec2
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/203390
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: 4eca47cd557b85259a1024658476ebdb4719804b
  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!