[roll] Roll fuchsia [build][sdk] Generate atom metadata at GN gen time

Generate, at `gn gen` time, enough information to rebuild the meta.json
for most IDK atoms.

Packages are not yet supported due to their use of content-based
hexadecimal hashes for file paths. This is fine for now since packages
are not built in the main "PLATFORM" build used by the Bazel in-tree
SDK.

Adds `source_prebuild_info` to the metadata of IDK atoms that do not
already include `value` in the metadata. The new
`idk_prebuild_manifest()` template, which is called for each IDK
collection, generates a prebuild manifest in `$OUT_DIR/sdk/prebuild/`.

The new `generate_prebuild_idk.py` script processes this file to
generate a `meta.json` file for each atom. It can be run immediately
after `fx gen` and before Ninja runs. Once an IDK collection build has
completed, the `--check` argument can be used to verify that the files
it generates match those created by Ninja.

Original-Bug: 338009514
Test: `fx build && build/sdk/generate_prebuild_idk/generate_prebuild_idk.sh --prebuild-manifest $(fx get-build-dir)/sdk/prebuild/in_tree_collection.json --build-dir $(fx get-build-dir) --check` passes.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1078492
Original-Revision: cb08447574f25c3d3997313470e268214f585cfb
GitOrigin-RevId: 80a54232c88179f2a0f0122c94fc0daba5ec3c4a
Change-Id: I9089e003621abb52725ad8c24d57729160a125f7
1 file changed
tree: 3fcabfffea8eaaab53d34465394752cbb9535766
  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.