A recent clang-roll (
crrev.com/c/2518420, November 4th) caused Chrome to stop building on Windows 7, with a "permission denied" failure on lld-link (tracked in
crbug.com/1150302). This wasn't intentional, but it was probably inevitable. It takes extra work to keep Chrome's development tools working on Windows 7, and breakage doesn't tend to be noticed because Google's build machines and developer machines have all been on Windows 10 for a while.
This isn't the first Windows 7 build-breakage this year and it feels like it might be time to call it - the maintenance cost is exceeding the benefits. If somebody feels strongly that building on Windows 7 is important then feel free to investigate the failure and propose a fix (presumably in the llvm repo) - we are generally willing to accept community contributions of this sort.
This does not change our support for running Chromium on Windows 7 - that is still supported. This is purely about
building chromium on Windows 7. If you need to test on Windows 7 you can build the mini_installer on Windows 10 (
or on Linux) and copy it to the Windows 7 machine.
Please reply here with any thoughts.
--