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: Fix env variable trim modes #90

Merged
merged 2 commits into from
Sep 4, 2023
Merged

Conversation

christophe-lunarg
Copy link
Contributor

@christophe-lunarg christophe-lunarg commented Sep 4, 2023

A setting can be accessed using env variables using the following order:
VK_LUNARG_TEST_MY_SETTING
VK_TEST_MY_SETTING
VK_MY_SETTING

VK_MY_SETTING mode was not working.

@christophe-lunarg christophe-lunarg merged commit 87801a6 into main Sep 4, 2023
20 checks passed
@christophe-lunarg christophe-lunarg deleted the fix-env-trim-mode branch September 4, 2023 14:54
Comment on lines +55 to +60
std::string result = GetAndroidProperty(variable);
// Workaround for screenshot layer backward compatibility
if (result.empty() && std::string(variable) == "debug.vulkan.screenshot.frames") {
result = GetAndroidProperty("debug.vulkan.screenshot");
}
return result;
Copy link
Contributor

@juan-lunarg juan-lunarg Sep 4, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kinda awkward to have this workaround in this repository just for the screen shot layer.

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

Successfully merging this pull request may close these issues.

2 participants