[roll] Roll fuchsia [sdk][bazel] Use separate subtools from bazel sdk

This makes it so that bazel can still use subtools from the sdk when
they're built separately by ensuring that the files that are relevant to
them are included in the hermetic copy of the sdk.

Original-Fixed: 125361
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/825217
Original-Revision: 1046a2bf0af860b94f1c5268959d8b933706b1d6
GitOrigin-RevId: dc2d1edf72c8d2b8fa03bb90e025be51ffc08cb2
Change-Id: I757eaf1c7af32e2bbc2be7ad62ad53da9f212042
1 file changed
tree: d25979a78bd6aa922c9087b7da2435a7bac51f90
  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.