Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2fdf6839a53d4cd6e6a4bce145534f36872f3c1e
commit2fdf6839a53d4cd6e6a4bce145534f36872f3c1e[log] [tgz]
authorRob Mohr <mohrr@google.com>Fri Jun 07 14:29:02 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 07 14:29:02 2024 +0000
treedf41d44864139bb79bc34a245963aa78ffaaae2a
parent1289ea830598de4e21d3910ae6d734b9c58ac8d7 [diff]
pigweed: Switch from submodule to Bazel import

Bug: b/323009830
Change-Id: I550d922615b85d47c24ffea8ceedcce484f40a5b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214511
Reviewed-by: Armando Montanez <amontanez@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Rob Mohr <mohrr@google.com>
3 files changed
tree: df41d44864139bb79bc34a245963aa78ffaaae2a
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. BUILD.bazel
  9. echo.bzl
  10. LICENSE
  11. pigweed.json
  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!