Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 061023c7db8c405b45827b5d2d87b7f0c2cf307e
commit061023c7db8c405b45827b5d2d87b7f0c2cf307e[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sat May 04 01:03:45 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat May 04 01:03:45 2024 +0000
tree9402f8383ae7c0281fc3d7f8bd9a91cb428cdf8d
parent784cb9c3c7a06a9a738fb9008aaf4cccf40f3ebb [diff]
[third_party/pigweed] Roll 6 commits

6c158d179f8e53b pw_log: Add core::fmt style format string support
f2bfca90d64a6d4 pw_bluetooth: Remove hci_vendor
664cea90c2e3998 pw_transfer: Lock resource_responder_ access
c3c31b852086eb2 docs: Update changelog
63761bcd7861acf pw_bluetooth_proxy: Reserve ACL LE slots from host
64d7ace864708ce pw_log: Rename Rust logging API to be less verbose

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 1f22c59e3a2f664..6c158d179f8e53b
Roller-URL: https://ci.chromium.org/b/8748911812967205057
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ia8502cbbcf5c08a3b24d29cb4f31a02e7c876d1b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208374
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 9402f8383ae7c0281fc3d7f8bd9a91cb428cdf8d
  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. 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!