[roll] Roll fuchsia [build][bazel] Introduce bazel_input_{file,directory}

Two new templates to simplify how Ninja outputs are exposed
to the Bazel graph through the @gn_targets repository.

Note that unlike bazel_input_resource_xxx() templates,
these do _not_ populate @legacy_ninja_build_outputs which
is now deprecated.

Future CLs will convert bazel_input_resource() targets
to bazel_input_file(), and bazel_input_resource_directory()
to bazel_input_directory(), which will allow the removal
of @legacy_ninja_build_outputs after that.

This will require multiple changes in fuchsia.git
but also some vendor/... repositories.

+ build/bazel/README.md: document the new scheme and
  provide a migration guide.

Original-Bug: 42074238
Original-Bug: 42082672
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1036776
Original-Revision: 216fc555453fc7c53d6bf04372bc0fbade1d4add
GitOrigin-RevId: 5866b93c270b40e9e111a5c36deefe26ef7371a2
Change-Id: I92fb60e412d7ed45ce4c4c9f4f6ea2db88d34f0e
1 file changed
tree: de0a5cc0861eb2a3491defcad982b5509f5b6f97
  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.