Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f93837a054e9d16f2e1e2e70cfebb27edcee0240
commitf93837a054e9d16f2e1e2e70cfebb27edcee0240[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jun 27 23:33:01 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 27 23:33:01 2024 +0000
treec8d22a5baca6ced2b1fc31b9168bfc0a696eed13
parente98291d19de23c7e8838aa807e909747f4803b1e [diff]
roll: pigweed, pw_toolchain 3 commits

0db899d70ac249e pw_bluetooth_sapphire: Add spec reference to comme
fdaad73494abbb9 pw_ide: Point to compile commands extractor fork
6cac32bea3a284b pw_rust: Static Library Linking

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