Google Git
Sign in
pigweed / pigweed / quickstart / bazel / df6eecc0868a915c3831c1b38737d283ef856e06
commitdf6eecc0868a915c3831c1b38737d283ef856e06[log] [tgz]
authorAaron Green <aarongreen@pigweed.infra.roller.google.com>Tue Jun 25 19:00:39 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 25 19:00:39 2024 +0000
treeb80388353c271323bffc2a7a67a5217d90623b76
parentac8688d3360ccef8dd55d8f602e3b625472473f7 [diff]
roll: pigweed, pw_toolchain: bazel: Encapsulate rp2040 WORKSPACE deps into deps.bazl

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/217219
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: fbb072a3e3d0a9b..5880c31b48ea299
Roller-URL: https://ci.chromium.org/b/8744132996374073937
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I72f19f43a10731dd8830886ed1a875b9dc92a20b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218253
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: b80388353c271323bffc2a7a67a5217d90623b76
  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!