Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2af111a30b6e5dec64aa5a6f15358b8eb69b4a84
commit2af111a30b6e5dec64aa5a6f15358b8eb69b4a84[log] [tgz]
authorTed Pudlik <tpudlik@google.com>Thu Jun 20 21:43:19 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 20 21:43:19 2024 +0000
tree56b2089ef0cf008d6d1697de238003595447eef6
parentc172da6e52c7b1ca0b88aa0b2421ccff527e7506 [diff]
bazel: Explicitly build some targets in presubmit

This will prevent skipping them due to accidental incompatibility
(https://pigweed.dev/bazel_compatibility.html#asserting-compatibility).

Test: bazelisk build --config=presubmit
Change-Id: I0a52e55f315d7a2607911fed82f5e896964470ba
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217134
Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Pigweed-Auto-Submit: Ted Pudlik <tpudlik@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Reviewed-by: Erik Gilling <konkers@google.com>
3 files changed
tree: 56b2089ef0cf008d6d1697de238003595447eef6
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!