Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 8d61a8edfeb2d2b6c360423aeede897f31d33063
commit8d61a8edfeb2d2b6c360423aeede897f31d33063[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Apr 22 18:54:19 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 22 18:54:19 2024 +0000
treedb623abf6aace05b6385fdf7550753624276bb55
parent762edee5b87ac68251e26caa62ad36cb7335b00b [diff]
[third_party/pigweed] Roll 5 commits

c8bdb2434d1efa8 pw_allocator: Add BumpAllocator
d128b112a1f7dd5 pw_cli: Add SEED creation to CLI tool
5f7e53a3f388446 emboss/CMakeLists.txt: Use COMPILE_LANGUAGE:CXX
6a9cc30b10a4ef8 docs: Require Bazel+GN+CMake for new contributions
cbb157a22f60e27 pw_snapshot: Fix bazel builds

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 0bfe65d4331f9ee..c8bdb2434d1efa8
Roller-URL: https://ci.chromium.org/b/8749931631655540977
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I0f7c2d77848c027b09594963cbeb6b1aaa360767
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205792
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: db623abf6aace05b6385fdf7550753624276bb55
  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!