After https://chromium-review.googlesource.com/c/412190/
we can remove all the GYP variables. The GN args are also not used
during runhooks (only GYP_DEFINES had any effect), so they're also
removed to avoid confusion. Only use_goma=True was left since
the ios recipe module uses it to decide if Goma shall be started
on the bots.
Delete unused GN/GYP-specific JSON files for bots that are now removed.
Finally, bump iOS version 10.0 and change simulator phones to
iPhone 6s to match what Chromium uses (may help solving bugs.webrtc.org/4752)
BUG=webrtc:4752, webrtc:6323
NOTRY=True
Review-Url: https://codereview.webrtc.org/2507063008
Cr-Commit-Position: refs/heads/master@{#15160}
Change the previous GN configs to build GYP instead
(since we'll keep GYP around for a while) but exclude tests
and examples for that config, since we'll only support the production
code for GYP.
Add new configs for upcoming rename of those bots to GYP instead
of GN.
BUG=webrtc:5949
NOTRY=True
TBR=ehmaldonado@webrtc.org
Review-Url: https://codereview.webrtc.org/2291443002
Cr-Commit-Position: refs/heads/master@{#13980}
Turns out that if mb_type is missing in the JSON, GYP is run the
traditional way instead of having the MB configuration decide.
This turns on MB for those builders.
See https://codereview.chromium.org/2194703002 for how Chromium
switched from GYP->GN.
The JSON environment for GYP and GN is only used during runhooks
step since there are scripts that key on some of these environment variables.
The actual build that is compiled is defined by the MB config, which
is now updated to have component=static_library everywhere for iOS.
With this CL, all configs gets a full GYP+GN environment.
When flipping bots over to GN, the following line will need to be added
in addition to changing mb_type:
"additional_compile_targets": [ "all" ],
Goma was also enabled for all builders to reduce compile time.
BUG=589510
NOTRY=True
Review-Url: https://codereview.webrtc.org/2239643002
Cr-Commit-Position: refs/heads/master@{#13775}
