Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 65afe45c00770c624e9ef42fa1d645e8b6d037ea
commit65afe45c00770c624e9ef42fa1d645e8b6d037ea[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 16 01:43:50 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 16 01:43:50 2024 +0000
treeacdc6bbc55e319928715902e63b7d96f61ef7f58
parentcf362fa216d33146eff8171c1974bdbc3e6cb082 [diff]
roll: pigweed, pw_toolchain 3 commits

0e7b3303a2e5b35 pw_console: Replace placeholder page with real web
a053780de153eee pw_web: NPM version bump to 0.0.20
4caae057c0fda46 pw_ide: Add IDE support refresh manager

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 28772428574c752..0e7b3303a2e5b35
Roller-URL: https://ci.chromium.org/b/8742295695059062353
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I39051f21b953a5f5003bb42b9c86c099bd40e03a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223240
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: acdc6bbc55e319928715902e63b7d96f61ef7f58
  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!