| commit | f558f6e3de9c89d205ff48fbf199ef114c6b3fb5 | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Fri Jul 19 05:37:37 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 19 05:37:37 2024 +0000 |
| tree | 3ccda0027bd75e67f9076e9f36609147feeed9a2 | |
| parent | 877e5c55c64306414d690958c070224535ee0d9c [diff] |
roll: pigweed, pw_toolchain: bazel: Use Python toolchain in custom rules This will make the bzlmod transition smoother (by removing the @python3 reference: in the bzlmod version of rules_python this repo doesn't exist any more). The Python toolchain is the right way to access the interpreter anyway. This is a reland of http://pwrev.dev/224272. The original change had an unlucky mid-air collision with http://pwrev.dev/204199. However, I also took the opportunity to fix the toolchain type to the exec_tools_toolchain_type (see https://pwbug.dev/258836641#comment59 for more). Original-Bug: 258836641 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/224298 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: e3076ba724ed431..e45ec8f7c2d1e77 Roller-URL: https://ci.chromium.org/b/8742009187639478177 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iba87e3a8be1774d6ce88a2a26a727c649ef6b750 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/224611 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
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.
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
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.
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!