Google Git
Sign in
pigweed / pigweed / quickstart / bazel / c0e85ae9f657db9ba7bd503c84ff25d5383936e0
commitc0e85ae9f657db9ba7bd503c84ff25d5383936e0[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Mar 28 00:33:03 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Mar 28 00:33:03 2024 +0000
tree4617715b921226f9e29ada2a79d9a1ecd539aab2
parent43d99cfbe45792aa47f14e87802e6ee72fd2e5d3 [diff]
[third_party/pigweed] Roll 6 commits

c00280eb8a57494 pw_minimal_cpp_stdlib: Clarify purpose
539d58908e3f09e *: Delete move constructors of buffer wrappers
6b5626d96ac20ef pw_presubmit: Switch format test data to importlib
c7637f55d0eb00a pw_env_setup: Run npm log viewer setup script afte
bd4160ce44435e4 pw_build: BuildRecipe auto_create_build_dir option
8818da6f3542896 docs: Simplify module creation docs using script

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f52852da66260fe..c00280eb8a57494
Roller-URL: https://ci.chromium.org/b/8752265846909062369
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iad43dd7a9b0a9ea25a2c6220c8739b1a9798b117
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200686
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 4617715b921226f9e29ada2a79d9a1ecd539aab2
  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!