| OLD | NEW |
| 1 # Windows Build Instructions | 1 # Windows Build Instructions |
| 2 | 2 |
| 3 ## Common checkout instructions | 3 ## Common checkout instructions |
| 4 | 4 |
| 5 This page covers Windows-specific setup and configuration. The | 5 This page covers Windows-specific setup and configuration. The |
| 6 [general checkout | 6 [general checkout |
| 7 instructions](http://dev.chromium.org/developers/how-tos/get-the-code) cover | 7 instructions](http://dev.chromium.org/developers/how-tos/get-the-code) cover |
| 8 installing depot tools and checking out the code via git. | 8 installing depot tools and checking out the code via git. |
| 9 | 9 |
| 10 ## Setting up Windows | 10 ## Setting up Windows |
| (...skipping 21 matching lines...) Expand all Loading... |
| 32 should work if its license is appropriate for you. Use the Custom Install option | 32 should work if its license is appropriate for you. Use the Custom Install option |
| 33 and select: | 33 and select: |
| 34 | 34 |
| 35 - Visual C++, which will select three sub-categories including MFC | 35 - Visual C++, which will select three sub-categories including MFC |
| 36 - Universal Windows Apps Development Tools > Tools | 36 - Universal Windows Apps Development Tools > Tools |
| 37 - Universal Windows Apps Development Tools > Windows 10 SDK (10.0.10586) | 37 - Universal Windows Apps Development Tools > Windows 10 SDK (10.0.10586) |
| 38 | 38 |
| 39 You must have the 10586 SDK installed or else you will hit compile errors such | 39 You must have the 10586 SDK installed or else you will hit compile errors such |
| 40 as redefined macros. | 40 as redefined macros. |
| 41 | 41 |
| 42 Install Windows Driver Kit (WDK) 10, or use some other method to get the |
| 43 Debugging Tools for Windows. |
| 44 |
| 42 Run `set DEPOT_TOOLS_WIN_TOOLCHAIN=0`, or set that variable in your | 45 Run `set DEPOT_TOOLS_WIN_TOOLCHAIN=0`, or set that variable in your |
| 43 global environment. | 46 global environment. |
| 44 | 47 |
| 45 Compilation is done through ninja, **not** Visual Studio. | 48 Compilation is done through ninja, **not** Visual Studio. |
| 46 | 49 |
| 47 ### Google employees | 50 ### Google employees |
| 48 | 51 |
| 49 Run: `download_from_google_storage --config` and follow the | 52 Run: `download_from_google_storage --config` and follow the |
| 50 authentication instructions. **Note that you must authenticate with your | 53 authentication instructions. **Note that you must authenticate with your |
| 51 @google.com credentials**, not @chromium.org. Enter "0" if asked for a | 54 @google.com credentials**, not @chromium.org. Enter "0" if asked for a |
| (...skipping 44 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 96 3. Store the build tree on a fast disk (preferably SSD). | 99 3. Store the build tree on a fast disk (preferably SSD). |
| 97 4. If you are primarily going to be doing debug development builds, you | 100 4. If you are primarily going to be doing debug development builds, you |
| 98 should use the component build. Set the [build | 101 should use the component build. Set the [build |
| 99 arg](https://www.chromium.org/developers/gn-build-configuration) | 102 arg](https://www.chromium.org/developers/gn-build-configuration) |
| 100 `is_component_build = true`. | 103 `is_component_build = true`. |
| 101 This will generate many DLLs and enable incremental linking, which makes | 104 This will generate many DLLs and enable incremental linking, which makes |
| 102 linking **much** faster in Debug. | 105 linking **much** faster in Debug. |
| 103 | 106 |
| 104 Still, expect build times of 30 minutes to 2 hours when everything has to | 107 Still, expect build times of 30 minutes to 2 hours when everything has to |
| 105 be recompiled. | 108 be recompiled. |
| OLD | NEW |