Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2421ab65c22cb60ceebf059758d32a9af201aad9
commit2421ab65c22cb60ceebf059758d32a9af201aad9[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Apr 19 00:50:49 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Apr 19 00:50:49 2024 +0000
tree03084cb58725c0e4226572232341ff3147c0631c
parentca0918ad0ae09ea6250f0327d8ee1d913b30854e [diff]
[third_party/pigweed] Roll 3 commits

b6d694586dbc0cd pw_unit_test: Add IWYU export/private pragmas
68ca4ccac262382 pw_bluetooth: Formatting fixes
e3662e8e52d2799 pw_kvs: Make Key an alias for string_view

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 463dca050a46608..b6d694586dbc0cd
Roller-URL: https://ci.chromium.org/b/8750271578590310865
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I40df65750e5de8017de45b515b6adf7541b4348f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204690
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: 03084cb58725c0e4226572232341ff3147c0631c
  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!