Google Git
Sign in
pigweed / pigweed / quickstart / bazel / bbb5fd93746b6becf0e9384c340d9150659e1a48
commitbbb5fd93746b6becf0e9384c340d9150659e1a48[log] [tgz]
authorAaron Green <aarongreen@pigweed.infra.roller.google.com>Fri May 17 19:14:46 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 17 19:14:46 2024 +0000
tree90beb401db2eb6a606adf6bcf03b10955b6c6c50
parent487da356d618d47821a2338a2110453c417b7fd3 [diff]
[roll third_party/pigweed] pw_allocator: Add AsPmrAllocator

This allows using PMR containers such as std::pmr::vector<T>.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/207170
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

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