Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 6cd8afced58b8ec21921151a079597474188013f
commit6cd8afced58b8ec21921151a079597474188013f[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Apr 18 00:50:00 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 18 00:50:00 2024 +0000
tree8d4263f501d3e5cdfacf89444570915d3ae8611e
parent06ab1110b6ac842ae429678feb28032795d54e6c [diff]
[third_party/pigweed] Roll 2 commits

c0fdef4a7e8c34c bazel: Use remote cache in infra
5aa6e0bbb727e1e pw_cli: Fix argument handling for GitRepo.has_unco

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f3b08caf413b2a7..c0fdef4a7e8c34c
Roller-URL: https://ci.chromium.org/b/8750362228386927153
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I5ac984f218e99202a83dee2845796db3e5e35b39
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204350
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 8d4263f501d3e5cdfacf89444570915d3ae8611e
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!