Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2e1a74c47faedb46e6790f3cd1a581172bdb90e7
commit2e1a74c47faedb46e6790f3cd1a581172bdb90e7[log] [tgz]
authorDavid Rees <drees@pigweed.infra.roller.google.com>Thu Jun 06 06:14:41 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 06 06:14:41 2024 +0000
treed7b8c4dd2f5f9bcf5512e7339b7bf92145ea2fe9
parentff5a9d4fa494586d4a38ecf3ebc3f7ca97897e6d [diff]
[roll third_party/pigweed] pw_bluetooth_proxy: Add maybe_unused to make downstream happy

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

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 7ddafaf90088efa..da7ee077f24a9bb
Roller-URL: https://ci.chromium.org/b/8745902545616635937
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Icdcd9fff27831fe63baec954331098a0104166c9
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214411
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: d7b8c4dd2f5f9bcf5512e7339b7bf92145ea2fe9
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  13. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!