Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 98bb169af76cdfaed538abdaae0fd5bf45d6de6c
commit98bb169af76cdfaed538abdaae0fd5bf45d6de6c[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Jul 18 00:24:39 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 18 00:24:39 2024 +0000
tree63481e7918aca9a79afc94ac546090e7460a2d0e
parentaef979b1b9135ba9539befdc5d483e25904ba022 [diff]
roll: pigweed, pw_toolchain 4 commits

003bbe28674612a pw_bluetooth_sapphire: Implement AcceptCis()
d01cc5df086d910 pw_chrono_freertos: Work around no std::unique_loc
7bd3905ad725850 roll: Fuchsia SDK
29eecebfec5d803 pw_bluetooth_proxy: Remove debugging log

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 64fab36c47fbac1..003bbe28674612a
Roller-URL: https://ci.chromium.org/b/8742119531606512113
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I09055a30824c5d0f2e4349cf21d714d6efe76692
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223800
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: 63481e7918aca9a79afc94ac546090e7460a2d0e
  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!