[roll] Roll fuchsia [superproject] Roll third_party/pigweed docs: How to use a single Pigweed module in Bazel

Provide some guidance on how to depend on Pigweed as "just a library"
from a pre-existing Bazel project.

In response to an old request from Kayce (sorry, internal-only link:
https://docs.google.com/document/d/1HkccKsBmC1IALJMszrLi9LBnK9mpHaiytL66txozVJU/edit?resourcekey=0-pIsK8e1pXn_CGdX-IYRyTg&disco=AAAA_QKPhdM)

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/188922
Original-Revision: 91075ebb2367073053be359a3baa17b9fa526b70
GitOrigin-RevId: 4e86a767a814e842cd182e2fe7576179626528ed
Roller-URL: https://ci.chromium.org/b/8757985734308445345
CQ-Do-Not-Cancel-Tryjobs: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/979873
Original-Revision: 4419f9fc0e92e13fecff4292d25b881199ce68fe
Change-Id: I4f3053632d6c1425c591a26e093500b0784e2edb
1 file changed
tree: c178b333a4b8de13e6c81f3f0f2efdf0d448d8e3
  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.