is the path of the directory containing the zip file (note that specifying scheme file:// is not required). Then, to use the generated file in a Linux or Mac host, the following environment variables need to be set: export DEPOT_TOOLS_WIN_TOOLCHAIN_BASE_URL= Note that if you didn't install the ARM64 components of the SDK as noted in the link above, you should add -noarm to the parameter list. Where and correspond respectively to the versions of Visual Studio (e.g. If you're not at GoogleĪfter installing Microsoft's development tools, you can package your Windows SDK installation into a zip file by running the following on a Windows machine: cd path/to/depot_tools/win_toolchain # Follow instructions, enter 0 as project id. Then you may need to re-authenticate via: cd path/to/chrome/src If this fails with an error: Please follow the instructions at Gclient sync should automatically download the Windows SDK for you. Gclient sync, follow instructions on screen. (If you already have a target_os line in there, just add 'win' to the list.) e.g. Tell gclient that you need Windows build dependencies by adding target_os = to the end of your. As a result, Crashpad cannot report crashes, and NaCl defaults to disabled and cannot be enabled in cross builds (.

on Mac hosts, 32-bit builds don't work ( bug has more information, and this is unlikely to ever change)Īll other targets build fine (including chrome, browser_tests.

js2gtest tests are omitted from the build ( bug).

This document describes how to set that up, and current restrictions. It’s also possible to run the locally-built binaries on swarming.

It‘s possible to build most parts of the codebase on a Linux or Mac host while targeting Windows. As many Chromium developers are on Linux/Mac, cross-compiling Chromium for Windows targets facilitates development for Windows targets on non-Windows machines.

Mac chromium