Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9cb159e1867f7c318c6395e20c1590ffb29c0511
commit9cb159e1867f7c318c6395e20c1590ffb29c0511[log] [tgz]
authorDavid Rees <drees@pigweed.infra.roller.google.com>Thu Mar 28 15:33:38 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Mar 28 15:33:38 2024 +0000
treed329b3c41edf14bc4dd012423278a2ca58eaeff8
parenta111c629d8f4d85247b5c09e43742f4bbf03640d [diff]
[roll third_party/pigweed] pw_bluetooth: Add cmake to usage guide

Test: Manual review of generated doc
Original-Bug: 326499587
Original-Bug: 326499650
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/200012

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 16ca90925a98bdc..b8c700540dbb7c0
Roller-URL: https://ci.chromium.org/b/8752209191229444849
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I881d9992f35e58148b052b3b12a6ea94498c86b3
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200895
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: d329b3c41edf14bc4dd012423278a2ca58eaeff8
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!