[roll] Roll fuchsia [idk] Reland "Build `vulkan_layers` only at LEGACY for now."

No changes, as this got caught up in a revert-stack.

`loadable_modules` (a.k.a., the "Vulkan layers") support being built at
individual API levels, but each of the subbuilds currently puts the
built libraries at the same path, so all but one of them gets clobbered.

My safer rewrite of "merge.py" noticed this, and is now throwing an
error. This change is a stop-gap mitigation to allow me to land the new
merger. Afterwards we'll take care of loadable_modules properly.

Having done a test build and diff, it appears that this doesn't change
anything about the final IDK itself.

Original-Bug: 316598209
Original-Bug: 327223536
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1024012
Original-Revision: 9079e8f718765f4355d6c8b539822e713424b582
GitOrigin-RevId: c3d3868c951307e1b3bd32175fa35b68b272cf4e
Change-Id: I0ac03ce446aca54939b059b3bd29acbf0e1b45ad
1 file changed
tree: dedecf0e6ffd069a19e8980bf7e0030d5ad616ad
  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.