Google Git
Sign in
pigweed / pigweed / quickstart / bazel / ca4cc9f30a0ef990ba2915efcd444e8c60b314e3
commitca4cc9f30a0ef990ba2915efcd444e8c60b314e3[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 17 18:33:25 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 17 18:33:25 2024 +0000
treee2d58e7987cfa0d8ecd9f71a61815fa2e39b54db
parent0ab9f7fb989b386115808938b2c3a64762c8f855 [diff]
roll: pigweed, pw_toolchain 2 commits

7dc26abc274fa80 pw_libcxx: Actually implement operator delete
b2afd53cde2dcc9 pw_ide: Revise docs

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 510f3669f3efa06..7dc26abc274fa80
Roller-URL: https://ci.chromium.org/b/8742141602178117745
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I281944f30a783eebd0e865ba880d634ec32ea27f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223796
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: e2d58e7987cfa0d8ecd9f71a61815fa2e39b54db
  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!