Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b0a7c32027b67cc892116dd9a5d073731e540d63
commitb0a7c32027b67cc892116dd9a5d073731e540d63[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jun 05 21:23:24 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 05 21:23:24 2024 +0000
treeb0e9ffb6b5b3ab13fa06d05960f914422f60a232
parent70e1fc28f90258a0e907667ec8c25e18b5a02051 [diff]
[third_party/pigweed] Roll 4 commits

52fa32ac0d460e0 pw_build: Update intro
f8259a3cb161f43 pw_spi_rp2040: Add module metadata
2803e38a0afeb3f pw_arduino_build: Add module metadata
3b855f66736b7a3 pw_ide: Preserve modified editor settings

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 46a21c419e5561f..52fa32ac0d460e0
Roller-URL: https://ci.chromium.org/b/8745936538067878209
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I29509d9a16dd0c1883e9bf0e2521b50e7a754068
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214271
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: b0e9ffb6b5b3ab13fa06d05960f914422f60a232
  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. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!