Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1d24c7b9bbbf37a6c6fc237549b4b77c9dddc738
commit1d24c7b9bbbf37a6c6fc237549b4b77c9dddc738[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jun 28 17:38:36 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 28 17:38:36 2024 +0000
tree9bd6de5b3ff481e5d17b73d948a7d7e12721edb3
parent538daac2330ae580d47d574804e29f8f792cdb95 [diff]
roll: pigweed, pw_toolchain 3 commits

5de4f11311a459e pw_system: Organize pw_system:async build targets
e6e4e3072a200da third_party/icu: Add Bazel build rules
9dffd008a348f4f pw_bluetooth_proxy: Remove use of <mutex>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 7b6c0f6c01c7584..5de4f11311a459e
Roller-URL: https://ci.chromium.org/b/8743866771384350977
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I981272330e864ca89eaa4b54c90537095e6b044f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/219011
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: 9bd6de5b3ff481e5d17b73d948a7d7e12721edb3
  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!