roll: pw_toolchain, pw_toolchain: Revert "roll: bazel"

This reverts commit 127b5fe73746c3858819beaad83d0416014ce627.

Reason for revert: broke things, should not have landed

Original change's description:
> roll: bazel
>
> From: version:2@7.1.2.7
> To: version:2@7.2.0.7
> Roller-URL: https://ci.chromium.org/b/8745043135247461473
> CQ-Do-Not-Cancel-Tryjobs: true
> Change-Id: Ib7d2d6ec5569c7c0c6766d4a9feae482aba116fd
> Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216334
> 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>

# Not skipping CQ checks because original CL landed > 1 day ago.

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

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: 8059f92ef1a93df..76f06970fcdd064
Roller-URL: https://ci.chromium.org/b/8744860083213195969
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie26c8a62b48a03ba672fef229f4f045b7c75b9c4
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216106
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: b2b1aecdbf0335e2f3ff425b03f7d815c82f0bc9
  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!