Google Git
Sign in
pigweed / pigweed / quickstart / gn / 2a4d79711171a02659142126585c896c8dbebecb
commit2a4d79711171a02659142126585c896c8dbebecb[log] [tgz]
authorRonan Chauvin <ronanchauvin@pigweed.infra.roller.gmail.com>Mon Apr 08 18:48:31 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 08 18:48:31 2024 +0000
treecd423e8272be940fb2d95739c69b1daa0a899830
parente0dc8450c75d3df17cfde3f77164a95570b1945a [diff]
[roll third_party/pigweed] pw_kvs: Add libraries to reuse partition and store tests for Bazel

To be able to test custom 'FlashMemory' implementations and it also
harmonize with GN build.

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

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