Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 7285b9c27898e3d8519dae112e238124d8a5dee1
commit7285b9c27898e3d8519dae112e238124d8a5dee1[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu May 02 01:02:20 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 02 01:02:20 2024 +0000
tree9e45c9b458778c6f68dc0509970fe450fba2227f
parentc7ed2c61343e3b9eb917b16bd0680f9279eb36a2 [diff]
[third_party/pigweed] Roll 3 commits

58a09c188df0cc6 pw_async2: Add AllocateTask
8c5103f3da47d9c pw_grpc: Remove old constructor after migration
962861dc8e2714c pw_build: CMake recipe for the pw build command

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 5bda8d1632020bd..58a09c188df0cc6
Roller-URL: https://ci.chromium.org/b/8749093120247702945
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib9d39f61d9b13dfca668be58cfcd51bd49ad087a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207583
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: 9e45c9b458778c6f68dc0509970fe450fba2227f
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!