Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9705d7bf8a6835fe098e2fdb114f0903f4e1f000
commit9705d7bf8a6835fe098e2fdb114f0903f4e1f000[log] [tgz]
authorAustin Foxley <afoxley@pigweed.infra.roller.google.com>Wed Jun 19 00:32:11 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 19 00:32:11 2024 +0000
treea4e61f7a7f9abe89252b21691a46783c8c6b6c6c
parentce37fc5d58000c52ad515a3491ec90b697e9adb0 [diff]
roll: pw_toolchain, pw_toolchain: pw_build_info: Add git_build_info.h header for embedding git info

Provides an autogenerated header derived from bazel workspace status
that lets you embed the git commit and tree status into an executable.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/213854
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: 2c8b44aa6836dd3..67b6c47a019a9ca
Roller-URL: https://ci.chromium.org/b/8744746380791076785
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic4455df57bd09b15767aa76410e86a63338f8539
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216822
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: a4e61f7a7f9abe89252b21691a46783c8c6b6c6c
  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!