Compile the Vulkan loader bridge with current V - #35
Merged
Merged
Conversation
This file contains hidden or 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
2 participants
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.
The current V compiler omits
loader_bridge.hwhen it is included only from the internalvulkan.cmodule. On Windows this leavesv_vulkan_initialize_loaderundefined when a consumer links with MSVC.Include the bridge from the public root module, where V reliably emits it, while keeping Volk's implementation in
c/volk.c.v.Validation on Windows 10 x64:
v -cc msvc test .(4/4 files passed)v -cc msvc run examples/ergonomic_lifecycle(created a Vulkan device on a GeForce GTX 765M)Merge dependency: merge #36 first so this PR reruns with the repaired pinned v3 bootstrap lane.