Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a70404bf22c771063911f61ba2bcd2a40560a0a5
commita70404bf22c771063911f61ba2bcd2a40560a0a5[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jul 22 21:19:11 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 22 21:19:11 2024 +0000
treef8314e1f746370588bd8743124d1680f5b053155
parent2b1d686b74895a38b65ca6e243488bd25177f277 [diff]
roll: pigweed, pw_toolchain 4 commits

6d21be2f13d7f84 pw_ide: Add missing command stubs
619b022b0c83feb pw_ide: Stream refresh compile commands output
2005f5e8a77fc3e pw_toolchain: Hide toolchain path behind variable
a70c899af249bc8 bazel: Remove sanitizers from default program

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 74bc3cad816843c..6d21be2f13d7f84
Roller-URL: https://ci.chromium.org/b/8741678187138715425
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3e9c2f9ea6bf3f9f54c661dc7579fc642118bcbb
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225431
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: f8314e1f746370588bd8743124d1680f5b053155
  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!