iOS buildbot configurations.

iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.
Buildbot changes are done in https://codereview.chromium.org/1659163003/

BUG=chromium:498746
NOTRY=True

Committed: https://crrev.com/8e85a3f39ad101c4fbe82b54253c8361c88f064a
Cr-Commit-Position: refs/heads/master@{#11468}

[smut, 2016-02-02 21:31:15]

smut@google.com changed reviewers:
+ smut@google.com

[smut, 2016-02-02 21:31:15]

This seems reasonable but I noticed something about one of your GYP_DEFINES
(applies to all .json configs).

Also keep in mind that the iOS recipe module currently has the directory where
these configs are located hard-coded:
https://chromium.googlesource.com/chromium/tools/build/+/5df39c3f68b4c6f27ba7...

You'll need to either change this directory structure to match or update
ios/api.py.

https://codereview.webrtc.org/1660053002/diff/20001/webrtc/build/ios/client.w...
File webrtc/build/ios/client.webrtc/iOS32_Simulator_Debug.json (right):

https://codereview.webrtc.org/1660053002/diff/20001/webrtc/build/ios/client.w...
webrtc/build/ios/client.webrtc/iOS32_Simulator_Debug.json:11: "target_arch":
"ia32"
I'm assuming you know your GYP_DEFINES are correct. Just FYI but on iOS we use
target_subarch instead of target_arch and we specify "arm32", "arm64", or
"both".

[kjellander_webrtc, 2016-02-02 22:28:29]

iOS recipe module actually already allowed passing in the paths as parameters to
the read_build_config function, so that's what I'm doing in
https://codereview.chromium.org/1659163003/ and it seems to have worked.

https://codereview.webrtc.org/1660053002/diff/20001/webrtc/build/ios/client.w...
File webrtc/build/ios/client.webrtc/iOS32_Simulator_Debug.json (right):

https://codereview.webrtc.org/1660053002/diff/20001/webrtc/build/ios/client.w...
webrtc/build/ios/client.webrtc/iOS32_Simulator_Debug.json:11: "target_arch":
"ia32"
On 2016/02/02 21:31:15, smut wrote:
> I'm assuming you know your GYP_DEFINES are correct. Just FYI but on iOS we use
> target_subarch instead of target_arch and we specify "arm32", "arm64", or
> "both".

Yeah, this is different for WebRTC, we only use target_arch (arm,arm64,ia32 or
x64) and then let target_subarch be set in
https://chromium.googlesource.com/external/webrtc/+/master/webrtc/supplement....
I don't remember exactly the details behind it, but it's been working so far. 
I'm not familar with exactly how the fat binaries and such works for iOS, but I
guess this could be improved in the future (so we align with how Chrome builds
this).

[kjellander_webrtc, 2016-02-02 22:28:55]

Description was changed from

==========
iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.

BUG=chromium:498746
==========

to

==========
iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.
Buildbot changes are done in https://codereview.chromium.org/1659163003/

BUG=chromium:498746
==========

[smut, 2016-02-02 22:31:36]

Seems lgtm

[kjellander_webrtc, 2016-02-03 08:02:04]

Description was changed from

==========
iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.
Buildbot changes are done in https://codereview.chromium.org/1659163003/

BUG=chromium:498746
==========

to

==========
iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.
Buildbot changes are done in https://codereview.chromium.org/1659163003/

BUG=chromium:498746
NOTRY=True
==========

[kjellander_webrtc, 2016-02-03 08:02:12]

The CQ bit was checked by kjellander@webrtc.org

[commit-bot: I haz the power, 2016-02-03 08:02:15]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1660053002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1660053002/80001

[kjellander_webrtc, 2016-02-03 08:03:15]

The CQ bit was unchecked by kjellander@webrtc.org

[kjellander_webrtc, 2016-02-03 08:04:50]

The CQ bit was checked by kjellander@webrtc.org

[commit-bot: I haz the power, 2016-02-03 08:04:54]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1660053002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1660053002/80001

[commit-bot: I haz the power, 2016-02-03 08:06:05]

Description was changed from

==========
iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.
Buildbot changes are done in https://codereview.chromium.org/1659163003/

BUG=chromium:498746
NOTRY=True
==========

to

==========
iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.
Buildbot changes are done in https://codereview.chromium.org/1659163003/

BUG=chromium:498746
NOTRY=True
==========

[commit-bot: I haz the power, 2016-02-03 08:06:06]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2016-02-03 08:06:12]

Description was changed from

==========
iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.
Buildbot changes are done in https://codereview.chromium.org/1659163003/

BUG=chromium:498746
NOTRY=True
==========

to

==========
iOS buildbot configurations.

This will make it possible for WebRTC to use the same buildbot
scripts as Chrome's iOS bots.
Buildbot changes are done in https://codereview.chromium.org/1659163003/

BUG=chromium:498746
NOTRY=True

Committed: https://crrev.com/8e85a3f39ad101c4fbe82b54253c8361c88f064a
Cr-Commit-Position: refs/heads/master@{#11468}
==========

[commit-bot: I haz the power, 2016-02-03 08:06:13]

Patchset 5 (id:??) landed as
https://crrev.com/8e85a3f39ad101c4fbe82b54253c8361c88f064a
Cr-Commit-Position: refs/heads/master@{#11468}