Upcoming Windows SDK Update
469 views
Skip to first unread message
Devon Loehr
Sep 27, 2024, 5:56:21 PM9/27/24
to Chromium-dev
We're currently working on updating the Windows SDK from version 10.0.22621.2428 to the newest version (10.0.26100.0). We'll push the update once we've ironed out the obvious issues, hopefully within the next week -- I'll send out a followup email when this happens.
No action is required at this time, but once the update lands everyone should make sure they're running the newest SDK version. For googlers, this should be automatic. We'll stop supporting the old SDK version once the patch has been stable for a little while (~1 week). I'll send out another email in advance.
--Devon Loehr
No action is required at this time, but once the update lands everyone should make sure they're running the newest SDK version. For googlers, this should be automatic. We'll stop supporting the old SDK version once the patch has been stable for a little while (~1 week). I'll send out another email in advance.
--Devon Loehr
Devon Loehr
Oct 16, 2024, 12:43:03 PM10/16/24
to Chromium-dev
Although it took longer than I'd hoped, the new Windows SDK update to version 10.0.26100.1742 has landed. Googlers can update their Windows toolchain by running `gclient sync` after pulling the changes. Non-googlers should install the SDK using their normal method (e.g. through Visual Studio, or from Microsoft's website).
For the next week or so, we're continuing to support SDK version 22621 on a best-effort basis: code should compile, but some tests may fail, in particular certain blink web tests that got new baselines during the update. Once we're confident the SDK update isn't going to get reverted, we'll remove support for the old SDK. I'll send out an email before we do so.
For anyone using an older version of Windows (1909 or earlier), note that we experienced failures during testing with dawn failing to load d3dcompiler_47.dll on x64 systems. This is because the DLL has begun dynamically linking the universal C Runtime (UCRT), and older versions of windows have older versions of the UCRT as well. To compensate, our packaged toolchain uses the DLL from SDK 22621 instead. For non-Googlers, if you encounter these failures, you can either update your UCRT, or use the 22621 version of the DLL as well. If anyone encounters similar failures on a non-x64 system, please let me know.
For the next week or so, we're continuing to support SDK version 22621 on a best-effort basis: code should compile, but some tests may fail, in particular certain blink web tests that got new baselines during the update. Once we're confident the SDK update isn't going to get reverted, we'll remove support for the old SDK. I'll send out an email before we do so.
For anyone using an older version of Windows (1909 or earlier), note that we experienced failures during testing with dawn failing to load d3dcompiler_47.dll on x64 systems. This is because the DLL has begun dynamically linking the universal C Runtime (UCRT), and older versions of windows have older versions of the UCRT as well. To compensate, our packaged toolchain uses the DLL from SDK 22621 instead. For non-Googlers, if you encounter these failures, you can either update your UCRT, or use the 22621 version of the DLL as well. If anyone encounters similar failures on a non-x64 system, please let me know.
--Devon Loehr
Reply all
Reply to author
Forward
0 new messages