Reuse an installed Vulkan SDK during setup - #34
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.
v run setup.vsh --installpreviously invokedwinget installeven when a valid Vulkan SDK was already present. Winget returns a nonzero "no upgrade available" result in that case, aborting setup for Vulkan and dependent modules.This change reuses a valid SDK from the current or machine
VULKAN_SDKvalue and invokes winget only when no usable installation is found.Validated on Windows 10 with Vulkan SDK 1.4.357.0: repeated
v run setup.vsh --installcompleted without changing the installed SDK.Merge dependency: merge #36 first so this PR reruns with the repaired pinned v3 bootstrap lane.