Workaround pre-instance functions on Android #53
Merged
Conversation
This file contains 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.
Pre-instance functions are not supposed to be intercepted, but Android
doesn't implement the better interface for chainable pre-instance
functions. Trying to intercept the vkEnumerateInstanceExtensionProperties
so a layer can query what extensions are available will not work
for any layer other than the bottom layer in the stack.
If you have multiple layers in installed, the higher layers will try
to use vkGetInstanceProcAddr to get the function in the next layer
down and get the stub implementation for the extensions the layer
itself implements without reaching the driver.