Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 7ec19279c4f92a6d3022a77be2a5d92aff5821a2
commit7ec19279c4f92a6d3022a77be2a5d92aff5821a2[log] [tgz]
authorAaron Green <aarongreen@pigweed.infra.roller.google.com>Thu Apr 25 15:56:24 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 25 15:56:24 2024 +0000
treec0f6ba860b8a47baf5251e85a4b0061c24fbf6c1
parent854af14b862c898e9b0dffda39b05f08f386686a [diff]
[roll third_party/pigweed] pw_allocator: Move FallbackAllocator implementation

Since FallbackAllocator is no longer templated, this CL moves its
implementation from the header to a source file.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/206174

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 54558a97edeb5ab..46f6477f64d1411
Roller-URL: https://ci.chromium.org/b/8749671013533479553
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I918b8125cde5de34fc3f97cf48d5a3d2029f5bd2
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206550
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: c0f6ba860b8a47baf5251e85a4b0061c24fbf6c1
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!