Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

layer_configuration.md does not describe programmatic configuration of layers #5895

Closed
KarenGhavam-lunarG opened this issue May 23, 2023 · 6 comments
Assignees

Comments

@KarenGhavam-lunarG
Copy link
Contributor

The file https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob/main/LAYER_CONFIGURATION.md does not explain how to enable layers programmatically. I think it should. This file is used by the SDK and referenced by all other layers in the SDK as the general guide on how to configure layers.

I know we are working on defining an API for programmatically configuring layers, should we wait to update this referenced documentation until that API is defined and made public? @christophe-lunarg

@mark-lunarg
Copy link
Contributor

The existing vk_layer_settings_ext.h allows setting layer options programmatically. When the updated version arrives with the rework the method will be very similar with the exception of having to include the header file.

@KarenGhavam-lunarG
Copy link
Contributor Author

See #5895. layer_configuration.md describes how to configure layers and is used in the SDK documentation and referenced by all SDK layers. I believe this document should be updated with how to configure layers programmatically.

@christophe-lunarg
Copy link
Contributor

christophe-lunarg commented May 23, 2023

Unless there is an explicit request from a user, I think we should way until the updated extenion is ready as this will be relatively soon. (No need to communicate too much on something that we are about to retire)

@juan-lunarg
Copy link
Contributor

Assigning @christophe-lunarg due to their recent work in VVL.

@christophe-lunarg
Copy link
Contributor

This issue is resolved by KhronosGroup/Vulkan-Utility-Libraries#85

@spencer-lunarg
Copy link
Contributor

as @christophe-lunarg said, this seems resolved and actually just missing someone closing the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants