[roll] Roll fuchsia [bazel][clang] Allow user-defined sysroot filegroups and paths

This is needed to migrate in-tree IDK generation from GN to Bazel, since
the migration will change some libraries from the sysroot to be built
with Bazel instead of GN, and a custom target will likely be needed to
generate the sysroot, which means we can no longer hardcode the paths to
Fuchsia sysroot in fuchsia_clang.

Default values are provided for newly add attributes to match existing
behavior.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1115432
Original-Revision: 46bb453a9668c4e7d2b8b0ee995aca19ac6ca68a
GitOrigin-RevId: d21329f0f9710cd76b852e08ad033b6c3f4fc90e
Change-Id: Iad09e8219783592ad0d144850b33999cbb2da7d3
1 file changed
tree: c7b533e3373d3c4444b922f31d2f77366dc620cb
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.