CI: Build Windows without D3D12 if install fails#113112
Merged
Repiteo merged 1 commit intogodotengine:masterfrom Nov 24, 2025
Merged
CI: Build Windows without D3D12 if install fails#113112Repiteo merged 1 commit intogodotengine:masterfrom
Repiteo merged 1 commit intogodotengine:masterfrom
Conversation
Repiteo
added
enhancement
platform:windows
topic:buildsystem
cherrypick:4.4
akien-mga
approved these changes
Nov 24, 2025
akien-mga
removed
the
cherrypick:4.4
Member
|
Cherry-picked for 4.5.2. |
akien-mga
removed
the
cherrypick:4.5
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.
Applies the same syntax and implementation details as the above PR, albeit for Direct3D 12 on Windows. Like the PR this is inspired by, this change will require manual verification of the logs to enture it's still being installed and enabled. Preliminary action outputs are operating as expected & the macOS step has worked without a hitch for months now, so this should be safe to integrate as-is