Google Git
Sign in
pigweed / pigweed / quickstart / bazel / eceaf222f24b7ab02e072aa8447d833e8300f089
commiteceaf222f24b7ab02e072aa8447d833e8300f089[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jun 20 22:47:56 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 20 22:47:56 2024 +0000
treec5c700bd7efbad19b4ce88793124059c52a94ae3
parent2727ee66213a8d67eb7b04fc41b84a2043653b1d [diff]
roll: pw_toolchain, pw_toolchain 3 commits

23df123c1a72c91 bazel: Update pin for rules_libusb
b1a86a0d336a1b0 pw_emu: Add bazel python build
d65c4f2ea2217b7 pw_toolchain: Add clippy-driver to rust toolchains

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: 1d9d180c93b9523..23df123c1a72c91
Roller-URL: https://ci.chromium.org/b/8744571690540466705
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic2f963b93e152d020ce867d02baf97e63e8261c8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217153
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: c5c700bd7efbad19b4ce88793124059c52a94ae3
  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!