Google Git
Sign in
pigweed / pigweed / quickstart / gn / f2f04d8c7af36709541d8f9790e56fbdc7ab549a
commitf2f04d8c7af36709541d8f9790e56fbdc7ab549a[log] [tgz]
authorErik Gilling <konkers@pigweed.infra.roller.google.com>Thu Apr 25 22:03:25 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 25 22:03:25 2024 +0000
tree13655f7ccce252406c549934602da8e21f48a26a
parentdec91f4b90e2b7f95bcfcc5b07e64eaa535c9f89 [diff]
[roll third_party/pigweed] pw_format: Better explain core::fmt whitespace parsing in ccomments

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/206671

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: a56e966f863779b..55f718e19c789f7
Roller-URL: https://ci.chromium.org/b/8749647944565391921
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I19e25d3f09a65d14b068f8a97395fa1e4fcba7f9
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206691
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: 13655f7ccce252406c549934602da8e21f48a26a
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!