Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9e31d562b74b0e54f96ba3becb291d4a00ccf1c4
commit9e31d562b74b0e54f96ba3becb291d4a00ccf1c4[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Tue Jul 23 03:10:06 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 23 03:10:06 2024 +0000
tree49a857f6c4c45c4b1778dc5591e8f3de5009af80
parentdf03fdde4c248e8002cea34b1ef5e3ffc338c9d0 [diff]
roll: pigweed, pw_toolchain: bazel: Move toolchain registration to MODULE.bazel

This will allow downstream projects to use these toolchains directly.

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 00d99767eb5ad66..ac64a18ef887e4b
Roller-URL: https://ci.chromium.org/b/8741656121116200433
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I57c12ec4cb49bc807d3a121e507498a187740026
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225376
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 49a857f6c4c45c4b1778dc5591e8f3de5009af80
  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!