commit | 0f3d3cacaceb755a72f6a39a1c2d5024673901cd | [log] [tgz] |
---|---|---|
author | Hunter Freyer <hjfreyer@fuchsia.infra.roller.google.com> | Tue Apr 09 18:48:31 2024 +0000 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 09 11:49:57 2024 -0700 |
tree | dedecf0e6ffd069a19e8980bf7e0030d5ad616ad | |
parent | ae38fc59495b7dbc252e6d119093a99186ddf3f4 [diff] |
[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
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party
.