Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b5e431fb80a1fa1d5149c73788d8d3bfd4aa750a
commitb5e431fb80a1fa1d5149c73788d8d3bfd4aa750a[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 17 06:07:30 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 17 06:07:30 2024 +0000
tree70a5329c46c06c80401932ed4a7a187fff1789d8
parentc8f8dfac7eca05f0c0a049f2f8d5045a07975f8b [diff]
roll: pigweed, pw_toolchain 2 commits

288cab865e0ce4e pw_string: Disable wchar test for libcpp
4efaa47db19bf11 pw_console: Handle web logging in a separate threa

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: bce5a2c840bcf60..288cab865e0ce4e
Roller-URL: https://ci.chromium.org/b/8742191336271696193
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I084c7ee6637c14c59918b6716fab69b6477911dc
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223544
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 70a5329c46c06c80401932ed4a7a187fff1789d8
  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!