Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2f67124c692d52422ca4af8d6c94e68fdab9e09b
commit2f67124c692d52422ca4af8d6c94e68fdab9e09b[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed May 08 19:07:40 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 08 19:07:40 2024 +0000
tree3dd8e3f9388879d67e3c1bdbaf896d5b1b00c506
parent9b29a60e90f4bcaf328b71253ec92c873cc8f5bf [diff]
[third_party/pigweed] Roll 5 commits

99192e42561f7d0 pw_tokenizer: Clean up rust docs
20da4adc3966443 pw_protobuf_compiler: Disable layering check less
7ef9f7009731d11 [fuchsia_infra] Roll 152 commits
ffab718375f979c pw_assert: Ensure condition does not contain stray
a3d96bad3957c08 pw_protobuf_compiler: Fix name collisions

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 1409f882b06e9e5..99192e42561f7d0
Roller-URL: https://ci.chromium.org/b/8748481227089661153
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ifeb0dc48861f962f5de370e63b6d214188b05cc9
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209073
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: 3dd8e3f9388879d67e3c1bdbaf896d5b1b00c506
  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!