Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d761c36b22b9835c0742db169b29a96297532dc0
commitd761c36b22b9835c0742db169b29a96297532dc0[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Fri Jul 19 23:21:29 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jul 19 23:21:29 2024 +0000
treec297a964752aa5b680bbc11a3bb45c874d7cb8a2
parentf9cd491b15b4e6b5d1a478e0d66a8e5082ccf45a [diff]
roll: pigweed, pw_toolchain: bazel: Modernize pip deps style (2)

Followup to http://pwrev.dev/223871.

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 4786d7910a0892f..d39a9561840c8fe
Roller-URL: https://ci.chromium.org/b/8741942284303072385
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id9aafc11e605fe0d2b2fa2fff57b72777ded881c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225131
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: c297a964752aa5b680bbc11a3bb45c874d7cb8a2
  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!