Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 3b99dd16fe080d2d944ffe861fe4ca8ac215a3c9
commit3b99dd16fe080d2d944ffe861fe4ca8ac215a3c9[log] [tgz]
authorChad Norvell <chadnorvell@pigweed.infra.roller.google.com>Tue Jun 04 01:34:14 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 04 01:34:14 2024 +0000
tree389f2830d9c6d4f4440a83ffa8fcd582ef40b297
parent9fa470cd137de92161cb3ed2061080f02536056b [diff]
[roll third_party/pigweed] pw_ide: Fix constant Pylance crashes

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

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 80a5042814f199d..d91003238d9cf8b
Roller-URL: https://ci.chromium.org/b/8746101387044143873
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I0ae795710d7487ac5c5cb6361b3d65826a6f6809
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213639
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 389f2830d9c6d4f4440a83ffa8fcd582ef40b297
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!