Google Git
Sign in
pigweed / pigweed / quickstart / bazel / bcad9d04ddf2783c93e014419c42a56746dbb15a
commitbcad9d04ddf2783c93e014419c42a56746dbb15a[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jun 20 19:53:55 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 20 19:53:55 2024 +0000
treed50201c7abb0ddde468c6a19608fc69b744153fa
parent9156f74791346f4abcce25a8d4f94c162aa805bd [diff]
roll: pw_toolchain, pw_toolchain 5 commits

0b2a6a9d699a848 nanopb: Import proto module
27b0e9eeeaffaea bazel: Update TODO in bazelrc
c6e8cd83c4dd6c0 pw_bluetooth_proxy: Fix naming of SetH4Type
325f9a48db05e1c pw_system: Rename target_io.cc
aa9d7a115b06c2f pw_web: Implement responsive toolbar behavior

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