Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 89da039867e85209b5dbefd45e2e56a8af9eefdb
commit89da039867e85209b5dbefd45e2e56a8af9eefdb[log] [tgz]
authorTaylor Cramer <cramertj@pigweed.infra.roller.google.com>Mon Jul 08 23:47:29 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 08 23:47:29 2024 +0000
tree2fab5c04f1cb4f554816fd4780b441ed67c6700d
parent6ec45b474d9a62b5b0226439154c8a2b24da6c7d [diff]
roll: pigweed, pw_toolchain: roll: Update Bazel to 7.2

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: c434a087580547b..6f7b53311728507
Roller-URL: https://ci.chromium.org/b/8742937205337658449
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib50d9106f4ad7964b0123ab2255a187e2ff65fa1
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220654
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: 2fab5c04f1cb4f554816fd4780b441ed67c6700d
  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!