Граф коммитов

10 Коммитов

Автор SHA1 Сообщение Дата
Mike Hommey dc5d1e6adf Bug 1335309 - Change the default for find_executables to False. r=mshal
Back when the class was written, for the packaging code, it made sense
that the default was True. But now that it's used all over the place,
and that the vast majority of uses are with find_executables=False, it
makes more sense for that to be the default.

--HG--
extra : rebase_source : ff813735fc0d53093f348f20eb77ee03e9b09d4e
2017-01-31 14:06:15 +09:00
Gregory Szorc 4702a9636e Bug 1283203 - Package Windows 10 Anniversary Update SDK; r=glandium
The Visual Studio installer now prompts to install Windows 10 SDK
10.14393.0, which corresponds to the SDK released with the Windows 10
Anniversary Update. Since it is the latest SDK available, let's start
packaging it instead of the older SDK in our standalone toolchain
archive.

MozReview-Commit-ID: 29T6hMHX18x

--HG--
extra : rebase_source : b22dba5f922dcbeb4147ac1a744c772e82e0e9ed
2016-09-09 09:55:44 -07:00
Mike Hommey 8ccc63df11 Bug 1289638 - Don't remove the SDK version from the SDK paths in the MSVC tooltool package. r=gps
While we're here changing the MSVC tooltool package, and since we're
going to remove the INCLUDE and LIB lines from mozconfigs that contain
the SDK version, we might as well make the SDK in the tooltool package
closer to an actual SDK, so that automation and local build more or
less follow the same (upcoming) configure code path.
2016-08-02 13:17:14 +09:00
Mike Hommey 843c82eecf Bug 1289638 - Don't rename the DIA SDK directory in the MSVC tooltool package. r=gps 2016-08-02 13:17:12 +09:00
Carsten "Tomcat" Book 480c0269ee Backed out changeset 0f6396641036 (bug 1289638) for breaking windows spidermonkey tests/builds 2016-08-01 09:12:55 +02:00
Carsten "Tomcat" Book f850d3a1a1 Backed out changeset ada66cbedd75 (bug 1289638) 2016-08-01 09:12:39 +02:00
Mike Hommey 439cf4860e Bug 1289638 - Don't remove the SDK version from the SDK paths in the MSVC tooltool package. r=gps
While we're here changing the MSVC tooltool package, and since we're
going to remove the INCLUDE and LIB lines from mozconfigs that contain
the SDK version, we might as well make the SDK in the tooltool package
closer to an actual SDK, so that automation and local build more or
less follow the same (upcoming) configure code path.

--HG--
extra : rebase_source : d760931fd721df1a6b27ae8caee37874eb1252f5
2016-07-28 16:53:44 +09:00
Mike Hommey fae208c213 Bug 1289638 - Don't rename the DIA SDK directory in the MSVC tooltool package. r=gps
--HG--
extra : rebase_source : 1082c4dc3423bebdbfb62d30c339043d994f47ba
2016-07-27 09:32:22 +09:00
Gregory Szorc c5b33d0cbb Bug 1259782 - Define zip archive path prefix argument; r=ted
To support generating zip archives with more flexibility.

MozReview-Commit-ID: LmAgAXUfn3x

--HG--
extra : rebase_source : 2b9ddbda0c3dab2a498b2fc217e728a9cfefc134
2016-04-22 11:37:14 -07:00
Gregory Szorc 432a47934a Bug 1253707 - Script to generate visual studio toolchain archive; r=ted
Previously, Windows toolchains and related dependencies (SDKs, etc)
were installed on Windows builders by people responsible for
maintaining those machines.

This commit takes a step in a new direction. We introduce a
script (complete with documentation) that can produce a zip
archive (or any archive format if people want to implement
support) of the toolchain files. Basically, you install
Visual Studio 2015 Community, run the script, and produce
a self-contained zip file containing everything from Microsoft
you need to build Firefox. With a copy of this archive and
an installation of MozillaBuild, it is possible to build
Firefox on a fresh Windows installation. No time-consuming
Visual Studio installation needed.

The goal is to upload these archives to tooltool and have
our Windows builders download and extract them at run-time.
At which time, we can remove all the other Visual Studio
and SDK files from builders because they don't need to be
baked into the image.

We may find tooltool's caching isn't good enough and we have
to more aggressively caching the standalone toolchain files.
But that is a problem for another day. Whatever happens,
we'll need the functionality in this script to produce
a self-contained archive of the toolchain.

There are certainly files in the produced archive that aren't
needed. I think perfect is the enemy of done and we can prune
the archive over time, if wanted.

MozReview-Commit-ID: EckEK1a6vA3

--HG--
extra : rebase_source : c328be792b2bfb4b3cb8acb50e4868277cb59974
extra : source : 4c980771e574e899a1b05319ad11fb6cffb00087
2016-03-11 15:00:02 -08:00