[roll third_party/pigweed] pw_containers: Omit size on FlatMap construction

- Adds a constructor and a template deduction guide to construct a
  FlatMap with Pair<K, V> objects without size.
- This method doesn't support 0 element because there is no type info
  for members of a pair.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/201030

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 36a94a20ffbaf42..e01ca5820679aeb
Roller-URL: https://ci.chromium.org/b/8749784321123104337
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I178deff74c48a3b448ce7d95addcd630e871295d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205994
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 9d9008b2db8ff56c6bdc98d25abf8dd52db59994
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  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!