Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 0dd0f69e578a3f23cbe009f179c78599847b5d30
commit0dd0f69e578a3f23cbe009f179c78599847b5d30[log] [tgz]
authorErik Gilling <konkers@pigweed.infra.roller.google.com>Tue May 07 22:26:14 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 07 22:26:14 2024 +0000
tree6312d2dffa9ce82ad13b4c1186f540a14a9f3aea
parent3b1a47d27b7beb6edf6408068eb80ea4431ed8fd [diff]
[roll third_party/pigweed] pw_format: Add test for escaped curly brackets

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/208291
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 6942dd5c53c11b4..4f0b1a7c4cd2ee2
Roller-URL: https://ci.chromium.org/b/8748560151643395889
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie8629045014d0f7ee53f6d65eea5d619f9138f3b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208794
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 6312d2dffa9ce82ad13b4c1186f540a14a9f3aea
  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. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. 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!