Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f30a6ba6041b3fb94b835fbf1f10a4945aba56f6
commitf30a6ba6041b3fb94b835fbf1f10a4945aba56f6[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 03 17:47:31 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 03 17:47:31 2024 +0000
tree9bfc9f1a6ac0536b5a682fa52ff9d59540e5f0fc
parent2776a1349a38499fb9df3465d2c8e9daf9f9930a [diff]
roll: pigweed, pw_toolchain: third_party/emboss: Update emboss to v2024.0702.215418

Fixes clangnext build failure.

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 4749e232d808939..4a79fe82a35e6b8
Roller-URL: https://ci.chromium.org/b/8743413146713474161
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I901b016dcc4067e18c68718ccf94d79eb3d07b37
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220151
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 9bfc9f1a6ac0536b5a682fa52ff9d59540e5f0fc
  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!