Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a7bf8e34b77648d28037fb53367296d0047c5180
commita7bf8e34b77648d28037fb53367296d0047c5180[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Aug 07 17:24:12 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 07 17:24:12 2024 +0000
tree58a3b59866c259ecf48a8ea903d84a509642585a
parent97b6c3a304104cdf2566b06c65d8d578a3f3bfe7 [diff]
roll: pigweed, pw_toolchain 4 commits

700cfaf609aa933 pw_bluetooth_sapphire: Fix statement expression ex
59eb77108667b32 pw_bluetooth_sapphire: Fix variadic macro warnings
c5a66b2e447524f pw_bluetooth: Improve ergonomics of emboss Support
37c87bbae3753e7 pw_digital_io: Add Mock

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 8436580deec2312..700cfaf609aa933
Roller-URL: https://ci.chromium.org/b/8740243771148579761
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If533fe27be186f3476ce337003c049425c906ff4
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/228171
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: 58a3b59866c259ecf48a8ea903d84a509642585a
  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!