Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 5f12ded9e9e3efad0d21aa773c61cde3f8141935
commit5f12ded9e9e3efad0d21aa773c61cde3f8141935[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 09 23:43:13 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 09 23:43:13 2024 +0000
treedda50ad0abfa7b1cac3552fccaa4f0e33daaf611
parentbf4db82e8a8d7a630f935768195ed1ee46506d9c [diff]
roll: pigweed, pw_toolchain 3 commits

7c60abf8f32f5cb pw_assert: Split up Bazel assert backend, part 2
211982ec49e2c55 pw_bluetooth_proxy: Delete "sendGattNotify"
418b923b27fbdc2 roll: Update Bazel to 8.0 rolling release

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: ebb087cf8898715..7c60abf8f32f5cb
Roller-URL: https://ci.chromium.org/b/8742847003752691553
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I196fde536aa9abb8076f8da8718c7677d616e7b6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220872
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: dda50ad0abfa7b1cac3552fccaa4f0e33daaf611
  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!