Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 95dd58e75b2a213c546619e14ec11862df07c74e
commit95dd58e75b2a213c546619e14ec11862df07c74e[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Apr 20 00:51:52 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Apr 20 00:51:52 2024 +0000
treec04a138a08a402a87217a57a1323dd2c4eb2b721
parentaee2c680353dbf441d113f92989584bf247d9819 [diff]
[third_party/pigweed] Roll 3 commits

98a790ed35ba482 pw_cli: Handle custom arguments in tools
d5104440ddda303 pw_bluetooth: Correct emboss path in doc example
7d13cb1075da395 pw_cli: Add git_repo.py and test to Bazel build

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 5da0b7bbfa9736d..98a790ed35ba482
Roller-URL: https://ci.chromium.org/b/8750180921659535313
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ia6faad385b171376774a8555c24893aca95e5fb0
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205030
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: c04a138a08a402a87217a57a1323dd2c4eb2b721
  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!