Update GYP to ffd524cefaad for MSVS 2017 (15)/C++ 14.1/C 19.10 support

aae1e3efb507 CQ config: add gerrit CQAbility verifier.
95da7665b1a3 [win-test] loosen win-driver-target-type test
eb296f67da07 [win] Add support for MS VS2017 (via Registry)
19495aa28282 Update test/no-cpp/gyptest-no-cpp.
a94b02ec68fb Disable a bunch of tests on Mac
ae76d9198630 Clean up gyptest.py
b62d04ff85e6 win,ninja: ninja generator better on windows
8dc77241251e Disable flaky test/copies/gyptest-all under msvs
e8850240a433 Fix MSVC++ 32-on-32 builds after b62d04ff85e6
ffd524cefaad win ninja/make: Always use a native compiler executable
             with MSVS 2017

developing.md is updated to call out supported toolchain versions, and
to explain the CDB requirement for end_to_end_tests.py.

Change-Id: Iace68009aa22acec7303ea02a2ded755645ea96c
Reviewed-on: https://chromium-review.googlesource.com/486539
Reviewed-by: Scott Graham <scottmg@chromium.org>
This commit is contained in:
Mark Mentovai 2017-04-25 12:41:49 -04:00
parent 4036e2c9d9
commit f31459b266
2 changed files with 21 additions and 4 deletions

2
DEPS
View File

@ -25,7 +25,7 @@ deps = {
'd62d6c6556d96dda924382547c54a4b3afedb22c',
'crashpad/third_party/gyp/gyp':
Var('chromium_git') + '/external/gyp@' +
'a7055b3989c1074adca03b4b4829e7f0e57f6efd',
'ffd524cefaad622e72995e852ffb0b18e83f8054',
# TODO(scottmg): Consider pinning these. For now, we don't have any particular
# reason to do so.

View File

@ -36,9 +36,14 @@ provides more detail.
To develop Crashpad, the following tools are necessary, and must be present in
the `$PATH` environment variable:
* Appropriate development tools. For macOS, this is
[Xcode](https://developer.apple.com/xcode/) and for Windows, its [Visual
Studio](https://www.visualstudio.com/).
* Appropriate development tools.
* On macOS, install [Xcode](https://developer.apple.com/xcode/). The latest
version is generally recommended.
* On Windows, install [Visual Studio](https://www.visualstudio.com/) with
C++ support and the Windows SDK. MSVS 2015 and MSVS 2017 are both
supported. Some tests also require the CDB debugger, installed with
[Debugging Tools for
Windows](https://msdn.microsoft.com/library/windows/hardware/ff551063.aspx).
* Chromiums
[depot_tools](https://dev.chromium.org/developers/how-tos/depottools).
* [Git](https://git-scm.com/). This is provided by Xcode on macOS and by
@ -191,6 +196,18 @@ $ cd ~/crashpad/crashpad
$ python build/run_tests.py out/Debug
```
### Windows
On Windows, `end_to_end_test.py` requires the CDB debugger, installed with
[Debugging Tools for
Windows](https://msdn.microsoft.com/library/windows/hardware/ff551063.aspx).
This can be installed either as part of the [Windows Driver
Kit](https://go.microsoft.com/fwlink/p?LinkID=239721) or the [Windows
SDK](https://go.microsoft.com/fwlink/p?LinkID=271979). If the Windows SDK has
already been installed (possibly with Visual Studio) but Debugging Tools for
Windows is not present, it can be installed from Add or remove programs→Windows
Software Development Kit.
### Android
To test on Android, use [ADB (Android Debug