Google Git
Sign in
pigweed / pigweed / quickstart / bazel / a7548a2f11a95b42ebacb4b5d4b0411b7d19d5e4
commita7548a2f11a95b42ebacb4b5d4b0411b7d19d5e4[log] [tgz]
authorAlan Rosenthal <alanrosenthal@pigweed.infra.roller.google.com>Tue Jun 18 21:37:24 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 18 21:37:24 2024 +0000
treed748e99a686cdd37a7d7ca474b0aa122f6f1c74c
parent7abb57de705db8a7c4d181d0715f50739ca1139c [diff]
roll: pw_toolchain, pw_toolchain: pw_ide: Run commands from PW_PROJECT_ROOT dir

Test: validate clangd integration with vscode

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216471
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: 49d5876907ba804..0af21c49fa7f692
Roller-URL: https://ci.chromium.org/b/8744757320744191137
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie90aedb0dce06dc02eb57a6aefe4e969981adcfb
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216871
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: d748e99a686cdd37a7d7ca474b0aa122f6f1c74c
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. BUILD.bazel
  9. echo.bzl
  10. LICENSE
  11. pigweed.json
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!