Added reporting of VK_KHR_external_memory_fd vulkan extension as feature #7825
+99
−21
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.
Connections
Builds on #7824 currently, but this requirement could probably be dropped if necessary.
Description
Previously, in order to check for support of
VK_KHR_external_memory_fd
vulkan extension, one had to useas_hal
and check the enabled extensions. However,VK_KHR_external_memory_win32
already reported this as a feature(even though both extensions are always enabled anyway). This PR brings that toVK_KHR_external_memory_fd
.Testing
No testing, very minimal changes
Squash or Rebase?
Both should be fine, as there is only one commit at the moment.
Checklist
cargo fmt
.taplo format
.cargo clippy --tests
. If applicable, add:--target wasm32-unknown-unknown
cargo xtask test
to run tests.CHANGELOG.md
entry.