roll: pigweed, pw_toolchain: pw_{kvs,result,tokenizer,unit_test}: Missing <string> includes
In libstdc++ string_view transitively includes string but in libc++
that's not the case and we need to include it explicitly which is
the correct approach (i.e. include-what-you-use).
Bugs: https://pwbug.dev/298822102
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/223352
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 789f3ef5abc6b6e..9d900358e89d603
Roller-URL: https://ci.chromium.org/b/8742240914256080801
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I8687814218b3a3bd1d954c136e860f4e1577f23c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223531
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: 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!