Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a6d4f0cdd537134d245d5166b18bbac862c86102
commita6d4f0cdd537134d245d5166b18bbac862c86102[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jun 24 23:17:34 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 24 23:17:34 2024 +0000
treeadfb1315b059c7d85c234e7bee70c4252c747f6b
parent8af4bb78cd29be4fcd24cfdf3d78a09fb698d7e6 [diff]
roll: pigweed, pw_toolchain 3 commits

3bf60a7ec0808b4 pw_preprocessor: Add docs metadata
942045675a03c39 pw_malloc: Add docs metadata
853213c54c4eeac pw_watch: Do not watch bazel-* symlinks

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