Skip to content

ci(prBuild): target 26100 SDK, and install the 26100 WDK#109

Merged
vdwtanner merged 1 commit into
mainfrom
user/tvandewalle/install-wdk-in-prbuild
May 21, 2026
Merged

ci(prBuild): target 26100 SDK, and install the 26100 WDK#109
vdwtanner merged 1 commit into
mainfrom
user/tvandewalle/install-wdk-in-prbuild

Conversation

@vdwtanner

@vdwtanner vdwtanner commented May 21, 2026

Copy link
Copy Markdown
Collaborator

PR build was failing because windows-latest runners ship Windows SDKs (10.0.22621.0 and 10.0.26100.0) but no WDK. D3D12TranslationLayer's DxbcParser transitively includes d3d12TokenizedProgramFormat.hpp, which only ships with the WDK.

Install the WDK matching CMAKE_SYSTEM_VERSION (10.0.22621.0) via winget (pre-installed on windows-latest). The 22621 WDK places its headers under the same Windows Kits\10\Include\10.0.22621.0 path the SDK uses, so CL picks them up with no extra include paths.

The verification step asserts the expected header lands at the expected path, so a future winget package-id rename trips a clear failure instead of an opaque C1083.

Resolves #97

@jenatali

Copy link
Copy Markdown
Member

Selecting Windows SDK version 10.0.26100.0 to target Windows 10.0.22621.0.

You'll need to add explicit CMake args to target the 22621 SDK.

@vdwtanner

Copy link
Copy Markdown
Collaborator Author

Selecting Windows SDK version 10.0.26100.0 to target Windows 10.0.22621.0.

You'll need to add explicit CMake args to target the 22621 SDK.

I'd thought -DCMAKE_SYSTEM_VERSION="10.0.22621.0" was supposed to do that, but maybe what I'm looking for is -DCMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION=10.0.22621.0?

@vdwtanner
vdwtanner force-pushed the user/tvandewalle/install-wdk-in-prbuild branch from d34de5b to 39cb918 Compare May 21, 2026 21:43
….hpp

PR build was failing because windows-latest runners ship Windows SDKs
(10.0.22621.0 and 10.0.26100.0) but no WDK. D3D12TranslationLayer's
DxbcParser transitively includes d3d12TokenizedProgramFormat.hpp,
which only ships with the WDK.

Install the WDK matching CMAKE_SYSTEM_VERSION (10.0.22621.0) via winget
(pre-installed on windows-latest). The 22621 WDK places its headers
under the same Windows Kits\10\Include\10.0.22621.0 path the SDK uses,
so CL picks them up with no extra include paths.

The verification step asserts the expected header lands at the expected
path, so a future winget package-id rename trips a clear failure instead
of an opaque C1083.

Resolves bug 58650349.
@vdwtanner
vdwtanner force-pushed the user/tvandewalle/install-wdk-in-prbuild branch from 39cb918 to 3827e07 Compare May 21, 2026 22:09

@jenatali jenatali left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should fix the title/description

@vdwtanner vdwtanner changed the title ci(prBuild): install WDK 22621 to provide d3d12TokenizedProgramFormat.hpp ci(prBuild): target 26100 SDK, and install the 26100 WDK May 21, 2026
@vdwtanner
vdwtanner merged commit 36ddb0d into main May 21, 2026
5 checks passed
@vdwtanner
vdwtanner deleted the user/tvandewalle/install-wdk-in-prbuild branch May 21, 2026 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build failing due to d3d12TokenizedProgramFormat.hpp not found while building dxbcparser

2 participants