Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 6ec45b474d9a62b5b0226439154c8a2b24da6c7d
commit6ec45b474d9a62b5b0226439154c8a2b24da6c7d[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jul 08 23:42:16 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 08 23:42:16 2024 +0000
tree6df3b8aafd6949c6d04f6f3299e785fc539c42b4
parent22e5cdb331bedbc76c334726714ac7b4720f778e [diff]
roll: pigweed, pw_toolchain 3 commits

c434a087580547b pw_allocator: Remove unnecessary template
6a928e54c51c63c pw_toolchain: Disable PIE for Golang
3178503b13226d7 pw_rpc: Expand comment for internal::ClientServerT

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 40ced78e4ae4490..c434a087580547b
Roller-URL: https://ci.chromium.org/b/8742937662635890417
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id64ea4f124ab33099034a781aaab7630d100e51c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220672
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 6df3b8aafd6949c6d04f6f3299e785fc539c42b4
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!