Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 333f8054f75ffe6c46949b070f60b70e4e12296e
commit333f8054f75ffe6c46949b070f60b70e4e12296e[log] [tgz]
authorErik Gilling <konkers@pigweed.infra.roller.google.com>Tue May 14 22:18:43 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 14 22:18:43 2024 +0000
tree2952a31d4ec7b588184d1730208704e8a31a08b2
parented7b9951d9394094362f30f3cf05c702181c4453 [diff]
[roll third_party/pigweed] pw_toolchain: Support Rust toolchains in downstream projects

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

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 077ce0610af5305..cd07cc170ebc110
Roller-URL: https://ci.chromium.org/b/8747926021461459217
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I441bd26de693e1448ac98f45bbb74e003b1b1b9b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209918
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 2952a31d4ec7b588184d1730208704e8a31a08b2
  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. 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!