Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d285a7399aa5e662aab81b67682123700f243589
commitd285a7399aa5e662aab81b67682123700f243589[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu May 09 01:07:54 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 09 01:07:54 2024 +0000
tree9198950e31d252fc7d21b309a4c4140f8f8bbcbd
parent9cf21738869bffb3382b9bbee888636c11d39cc7 [diff]
[third_party/pigweed] Roll 2 commits

cbb3917c36a4f77 emboss: Use absolute paths in source dependencies
0594139badff8c9 pw_ide: Add .pw_ide.user.yaml to .gitignore

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