Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f97cc372610d8af67f55d696ad6b306c615e661b
commitf97cc372610d8af67f55d696ad6b306c615e661b[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 17 01:07:50 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 17 01:07:50 2024 +0000
tree16a958473668735eca1011d24ca9ae1f01b50f74
parentd53751eca7434e1a0e85354cfb43c59dd00d8e17 [diff]
roll: pigweed, pw_toolchain 3 commits

d616e78205d88ba pw_unit_test: Update logging_main compatibility
2766aa101c6e187 pw_libcxx: Add operator new
73a7627c588b5de pw_presubmit: Allow disabling checks in unit tests

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