[roll] Roll fuchsia [build][sdk] Clarify targets related to in-tree IDK and SDK

There are various targets named "bazel_in_tree_idk" and
"in_tree_fuchsia_sdk", but some of them are only for comparison tests -
something that might not be obvious. Rename test-only targets and add
comments to clarify this.

Also revert the target formerly known as "bazel_in_tree_idk.bazel_input"
to use a Ninja-based IDK. https://fxrev.dev/1246990 changed it to use
`regenerator_outputs`, but that is the Bazel IDK to which it is being
compared.

Make the actual "in_tree_fuchsia_sdk" target depend on
"//sdk:bazel_in_tree_idk", which will populate the symlink targets of
the IDK generated by regenerator.py.

Original-Bug: 338009514
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1255351
Original-Revision: d5c29dfc3b247008802ff1aa9a2f7f395ab5bcb9
GitOrigin-RevId: 887d247739a061a0d86ab46051e6f6fcadafdab9
Change-Id: I33422baa71302e03f014d9243ff5ddda6984976c
1 file changed
tree: 8ae4ef16881c0fe83a916eeb51e6ca664599b812
  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 in one of the communication channels documented at get involved.

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.