Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 555d9af9e12a53f7d967a11bdec8034e2fdc8d93
commit555d9af9e12a53f7d967a11bdec8034e2fdc8d93[log] [tgz]
authorTaylor Cramer <cramertj@pigweed.infra.roller.google.com>Wed Jul 31 21:43:22 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 31 21:43:22 2024 +0000
treebd15da76638f17f0e0e94b7470f03cfc3e02b871
parent6b9607e95095a4c41a0501b026d4c0c8818e561b [diff]
roll: pigweed, pw_toolchain: pw_symbolizer: Add missing runfiles dep

Original-Bug: b/355527449
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/226719
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 59f96058375492f..0e17c001aa2a1c6
Roller-URL: https://ci.chromium.org/b/8740861274693803601
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I7906bc1128e82a513f8bc8b780a69731c1d8c450
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226898
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: bd15da76638f17f0e0e94b7470f03cfc3e02b871
  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!