Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f9cd491b15b4e6b5d1a478e0d66a8e5082ccf45a
commitf9cd491b15b4e6b5d1a478e0d66a8e5082ccf45a[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jul 19 23:14:39 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jul 19 23:14:39 2024 +0000
treeb4af32fe907505bcc2a8cef65b3a1d21956a632d
parent019cd2adc93bf2546a5866440a5b4afceb61d84a [diff]
roll: pigweed, pw_toolchain 3 commits

4786d7910a0892f go: Create a Pigweed-wide go.mod file
449b11f8aab03df pw_bluetooth_proxy: Update emboss deps
b7a3c2e0f93fbb0 pw_ide: Update dev build configs

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: f6c4828aa0db15b..4786d7910a0892f
Roller-URL: https://ci.chromium.org/b/8741942993737239121
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3c2b81141c2c3e02a96a3e683a71f65b6c042267
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225092
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: b4af32fe907505bcc2a8cef65b3a1d21956a632d
  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!