Google Git
Sign in
pigweed / pigweed / quickstart / bazel / db904c538c5028d044bbbfdeef4987397d08104c
commitdb904c538c5028d044bbbfdeef4987397d08104c[log] [tgz]
authorPetr Hosek <phosek@pigweed.infra.roller.google.com>Wed May 08 10:07:23 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 08 10:07:23 2024 +0000
treea7bf9637ed9b078f91042fcc5604948c24474b2d
parent7878b052aa70174df3ac8622076ae54771b7a132 [diff]
[roll third_party/pigweed] pw_libcxx: Minimal implementation

Provide a minimal pw_libcxx implementation that uses LLVM libc++.

Bugs: https://pwbug.dev/298822102
Docs: N/A
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/201918
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 188876aa96f12be..258066a475ea2cf
Roller-URL: https://ci.chromium.org/b/8748515225177628849
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I12adae969c82e574278ec9a6d5e1d69c52edce45
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209011
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: a7bf9637ed9b078f91042fcc5604948c24474b2d
  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!