commit | fca8e8720feecf9faa988b92806b574cd530b23e | [log] [tgz] |
---|---|---|
author | Devon Loehr <dloehr@google.com> | Thu Mar 20 16:54:01 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 20 16:54:01 2025 |
tree | 2fdb13e8fd9c0808540ab3cc05333e14d6289e3f | |
parent | b3fe2feb9c0449a574d8c3bbfaf4060f1e0e853c [diff] |
Update Supported Windows SDK to 10.0.26100.3323 The floor bug (https://crbug.com/374162585) which blocked the previous roll has been addressed, so we're trying to update the SDK again. Code changes are essentially the same as the previous update attempt (https://crrev.com/c/5898835). Some minor changes to gate new SDK features behind a #define while we transition, and some regenerated image baselines to support the new 3D emojis. Note that updating mc.exe and midl.exe outputs produced no changes. Pleasantly, the linking change to d3dcompiler_47.dll has been undone, so we no longer need to patch in an older version. This means the update is about as straightforward as it gets. ----------------------------------------------------------------- Instructions to reproduce: These instructions are best done on a fresh VM. Make sure to uninstall any existing installations of Visual Studio and any existing SDK installations before starting. 1. Install git for windows from their website, with the default settings (https://git-scm.com/downloads/win) 2. Install depot_tools following the instructions on their webpage (https://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/depot_tools_tutorial.html#_setting_up) 3. Run: $ git config --global depot-tools.allowGlobalGitConfig true 4. Download Visual Studio Professional (Free Trial) from the official site (https://visualstudio.microsoft.com/downloads/) 5. Run the VS installer with the following arguments: ``` $ VisualStudioSetup.exe --add Microsoft.VisualStudio.Workload.NativeDesktop --add Microsoft.VisualStudio.Component.VC.ATLMFC --add Microsoft.VisualStudio.Component.VC.Tools.ARM64 --add Microsoft.VisualStudio.Component.VC.MFC.ARM64 --includeRecommended --passive ``` 6. Open the VS installer (from the start menu), click “Modify”, and uninstall any existing SDK versions (search for “windows sdk”). 7. Open “Add or Remove Programs” and make sure there are no SDK versions installed; remove them if so (search for “windows software development kit”). 8. Download SDK Version 10.0.26100.3323 from the official site (https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/) 9. Run the SDK installer with default settings, except disable “insights”. 10. Run the packaging script from depot_tools, e.g $ python3 depot_tools\win_toolchain\package_from_installed.py 2022 -w 10.0.26100.0 Link to packaging script version used for packaging: https://source.chromium.org/chromium/chromium/tools/depot_tools/+/main:win_toolchain/package_from_installed.py;drc=371aa997c04791d21e222ed43a1a0d55b450dd53 This resulted in the final package with hash 076960eda6. Bug: 362650376 Change-Id: Ib6cb299ab20cfca1e72f34728e6ea165ab057d05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6252774 Reviewed-by: Keren Zhu <kerenzhu@chromium.org> Reviewed-by: Dominic Farolino <dom@chromium.org> Reviewed-by: Zequan Wu <zequanwu@google.com> Commit-Queue: Devon Loehr <dloehr@google.com> Reviewed-by: Giovanni Ortuno Urquidi <ortuno@chromium.org> Reviewed-by: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/main@{#1435503}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.