mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-09 19:35:51 +00:00
ba049d3406
This commit switches Windows builds from Visual Studio 2013 to Visual Studio 2015 Update 1. Previously, Visual Studio was installed on the builders as part of the base system image. Starting with this commit, we obtain Visual Studio from a pre-generated, self-contained archive containing the executables, Windows SDK, and other support files. This means that new Windows toolchains can be installed without having to modify configuration of machines in automation! The mozconfigs for Visual Studio 2015 are a bit different from existing mozconfigs. Because it appears to be completely redundant and not necessary, the LIBPATH variable has been dropped. The order of paths in PATH, LIB, and INCLUDE has changed. The new order more accurately reflects what would be defined by vcvarsall.bat. As part of switching to Visual Studio 2015, the Universal CRT is now required. So, the 2015 mozconfigs export WIN_UCRT_REDIST_DIR to define the location to those files. The switch to Visual Studio 2015 also involves the switch from the Windows 8.1 SDK to the Windows 10 SDK. However, we still target an old version of Windows, so this hopefully shouldn't have any significant fallout. It's worth noting that switching to Visual Studio 2015 makes builds - especially PGO builds - significantly faster. Our PGO build times in automation are ~1 hour faster. Our regular builds appear to be a few minutes faster. MozReview-Commit-ID: Pa5GW8V87Q --HG-- extra : source : 56b27306d3257445f70374aa78fc5bd42ef300ce extra : intermediate-source : 559a80645f20706e1eaaeed863e90c2d35ff7644
26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
# To trigger a clobber replace ALL of the textual description below,
|
|
# giving a bug number and a one line description of why a clobber is
|
|
# required. Modifying this file will make configure check that a
|
|
# clobber has been performed before the build can continue.
|
|
#
|
|
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
|
|
# merge both CLOBBER descriptions, to ensure that users on
|
|
# both branches correctly see the clobber warning.
|
|
#
|
|
# O <-- Users coming from both parents need to Clobber
|
|
# / \
|
|
# O O
|
|
# | |
|
|
# O <-- Clobber O <-- Clobber
|
|
#
|
|
# Note: The description below will be part of the error message shown to users.
|
|
#
|
|
# Modifying this file will now automatically clobber the buildbot machines \o/
|
|
#
|
|
|
|
# Are you updating CLOBBER because you think it's needed for your WebIDL
|
|
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
|
|
# don't change CLOBBER for WebIDL changes any more.
|
|
|
|
Bug 1114647 - Renamed the content process
|