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

Reasses the requirement that meta layer components must have the same API version #796

Closed
charles-lunarg opened this issue Jan 20, 2022 · 1 comment · Fixed by #901
Closed
Labels
question

Comments

@charles-lunarg
Copy link
Collaborator

@charles-lunarg charles-lunarg commented Jan 20, 2022

This issue is a tracking issue for whether there needs to be change to the requirement that meta layers must have the same API version across all component layers.

The reason is that this requirement limits the applicability of meta layers, since it restricts the layers to ones that share the same API version.

I think a more flexible policy is that all component layers must have an API version that is greater than or equal to the API version in the meta layer. This is because of the loader behavior which removes implicit layers whose API version is less than the API version specified in VkInstanceCreateInfo.

@charles-lunarg charles-lunarg added the question label Feb 15, 2022
@charles-lunarg
Copy link
Collaborator Author

@charles-lunarg charles-lunarg commented Mar 25, 2022

I think it is reasonable for meta layers to define the 'minimum' API version. Thus all component layers must match or exceed that version. Them being equal doesn't really affect the ability for the layers to be active. As long as all the layers support the API version the application requests (which predicates whether the meta layer is activated or not) it should be fine.

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

Successfully merging a pull request may close this issue.

1 participant