Repository navigation
Remove Meta-Layers - add Layer Manifest File Format Version 1.2.2 - #2079
Merged
charles-lunarg merged 1 commit intoOct 23, 2026
Merged
Conversation
Meta layers are not widely used in the ecosystem - the two main uses for them were for the VK_LAYER_LUNARG_standard_validation (which was removed in ~2019) and the VK_LAYER_LUNARG_override special meta layer that was used by VkConfig (removed 2024 with the addition of the Loader Settings file.) They greatly complicate the code by introducing a layer type that, while being processed, can cause other layers to be enabled. They required recursive functions to handle meta-layers enabling other meta layers. Their presence required special handling when processing normal layers. Amended the docs to drop most description of Meta Layers, keeping only the minimal required in case someone finds one in the wild. Added Version 1.2.2 of the Layer Manifest File Format, which describes the changes to the layer manifests - specifically dropping the fields associated with meta-layers and specifying that `"library_path"` is required once again.
|
CI Vulkan-Loader build queued with queue ID 168416. |
|
CI Vulkan-Loader build queued with queue ID 168433. |
|
CI Vulkan-Loader build # 3902 running. |
|
CI Vulkan-Loader build # 3902 passed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Meta layers are not widely used in the ecosystem - the two main uses for them were for the VK_LAYER_LUNARG_standard_validation (which was removed in ~2019) and the VK_LAYER_LUNARG_override special meta layer that was used by VkConfig (removed 2024 with the addition of the Loader Settings file.)
They greatly complicate the code by introducing a layer type that, while being processed, can cause other layers to be enabled. They required recursive functions to handle meta-layers enabling other meta layers. Their presence required special handling when processing normal layers.
Amended the docs to drop most description of Meta Layers, keeping only the minimal required in case someone finds one in the wild.
Added Version 1.2.2 of the Layer Manifest File Format, which describes the changes to the layer manifests - specifically dropping the fields associated with meta-layers and specifying that
"library_path"is required once again.