[roll] Roll third_party/pigweed pw_malloc: Require specifying a backend in bazel build

Now that all downstream users of this interface are using the
constraint_setting to select a valid backend, we can require one to be
selected.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/185441
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: cf6b92b217407cef85824e3881542d65d0109867
GitOrigin-RevId: 439cf11392a311cf5cd3e561004df9364a7937ee
Change-Id: Ie9e8e552a28aba9c276fddf4fa272a4517a0579a
1 file changed
tree: 2d1f47a8edef704fba1992d6e0ca7a59bffe6f12
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.