Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 7295a3246e5f066c101f96a75591a4ea4a8c6229
commit7295a3246e5f066c101f96a75591a4ea4a8c6229[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Wed Jul 17 18:39:17 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 17 18:39:17 2024 +0000
tree6f45ae1440b4a5e8b45417e641d0876026acd093
parentca4cc9f30a0ef990ba2915efcd444e8c60b314e3 [diff]
roll: pigweed, pw_toolchain: pw_toolchain: Add linux_sysroot.bzl

This makes the code more robust against canonical repo changes, and is
necessary for supporting both bzlmod and WORKSPACE users.

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 7dc26abc274fa80..a98647d744dc24c
Roller-URL: https://ci.chromium.org/b/8742141210263919105
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I6d2d1db60be5a7a0d5bdfa08e408010a0536e0b5
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223971
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: 6f45ae1440b4a5e8b45417e641d0876026acd093
  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!