Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 15960dc4cc0471b64aa5ea43315d8035e2dda2e6
commit15960dc4cc0471b64aa5ea43315d8035e2dda2e6[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat Apr 27 00:57:44 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Apr 27 00:57:44 2024 +0000
treefdaf1fa7a5ba01d33c55d2dda6c1b4dbc875b07c
parent9e515aff347c9baadeec864c3e9f91faa891756f [diff]
[third_party/pigweed] Roll 3 commits

188bd4726e0eca3 *: Remove remaining usages of legacy thread entry
74004ce5958687a pw_async: Add missing dispatcher facades to cmake
ae56930feef9426 fuchsia: Add defer.h to Bazel build defs

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 9e90af3746446e4..188bd4726e0eca3
Roller-URL: https://ci.chromium.org/b/8749546372717087377
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If2a632acd36921f01aff3fa92511032e2ea16eed
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206878
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: fdaf1fa7a5ba01d33c55d2dda6c1b4dbc875b07c
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!