Google Git
Sign in
pigweed / pigweed / quickstart / bazel / e0ae9c5a74d7a4ed604e9b2248b62d1191b34e14
commite0ae9c5a74d7a4ed604e9b2248b62d1191b34e14[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed May 29 01:23:05 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 29 01:23:05 2024 +0000
tree875b22af4d12aa50df413b0fb909d744920a2820
parent023bb977d297994e552737bed76ab2053045b851 [diff]
[third_party/pigweed] Roll 2 commits

69fa240add6d3f3 pw_libcxx: Only enable in clang builds
ffaaf974d53a74a bazel: Update rules_rust to 0.45.1

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: c2915194debfc14..69fa240add6d3f3
Roller-URL: https://ci.chromium.org/b/8746645667614392225
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1f3bb0f218a8f191f6fe64b4bc6766c80d4b7114
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/211943
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 875b22af4d12aa50df413b0fb909d744920a2820
  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!