Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 74c482b95b2fbd57d85ef77b2869490475c1c977
commit74c482b95b2fbd57d85ef77b2869490475c1c977[log] [tgz]
authorRob Mohr <mohrr@google.com>Tue Jun 04 16:04:34 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 04 16:04:34 2024 +0000
tree0e6cea53d17dc34ee11618df63284a5081b76c67
parent0c87287726895c3ba7c0be7b59b064d0f5171d6a [diff]
Add presubmit programs to pigweed.json

Bug: b/275107504
Change-Id: Ice9b5bdd2c929a9e1cc1a29f938e69c33b4c6573
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213641
Reviewed-by: Ted Pudlik <tpudlik@google.com>
Commit-Queue: Rob Mohr <mohrr@google.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 0e6cea53d17dc34ee11618df63284a5081b76c67
  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. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!