Added coverage support for all iOS targets.

Added coverage support for all iOS targets.

build/ios/coverage.gypi is conditionaly included into build/common.gypi
for iOS platform.

BUG=441961
Committed: https://crrev.com/f24d6e272a97eab52bc27322e07d4160ece83408
Cr-Commit-Position: refs/heads/master@{#312983}

[Eugene But (OOO till 7-30), 2015-01-23 19:31:36]

eugenebut@chromium.org changed reviewers:
+ thakis@chromium.org

[Nico, 2015-01-23 21:38:15]

Every time you do something that spans more than 1 cl, please create a tracking
bug for that and reference it in all cls that are related to it (in this case,
"coverage for chromium/ios", i suppose)

Change lgtm.

Is this enough for me to repro the problems you were seeing with chromium's
clang?

[Eugene But (OOO till 7-30), 2015-01-23 23:43:13]

On 2015/01/23 21:38:15, Nico wrote:
> Every time you do something that spans more than 1 cl, please create a
tracking
> bug for that and reference it in all cls that are related to it (in this case,
> "coverage for chromium/ios", i suppose)
Updated the issue with our internal bug.

> Is this enough for me to repro the problems you were seeing with chromium's
> clang?
I think the following steps should reproduce the problem:
1.) Run: mkdir -p ~/.gyp && echo
'{"variables":{"enable_coverage":1,"clang_xcode":0,}}' > ~/.gyp/include.gypi &&
gclient runhooks
2.) Compile ios_chrome_unittests target

Thanks!

[Eugene But (OOO till 7-30), 2015-01-23 23:43:17]

The CQ bit was checked by eugenebut@chromium.org

[commit-bot: I haz the power, 2015-01-23 23:44:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/867323003/1

[Nico, 2015-01-23 23:59:19]

On 2015/01/23 23:43:13, eugenebut wrote:
> On 2015/01/23 21:38:15, Nico wrote:
> > Every time you do something that spans more than 1 cl, please create a
> tracking
> > bug for that and reference it in all cls that are related to it (in this
case,
> > "coverage for chromium/ios", i suppose)
> Updated the issue with our internal bug.
> 
> > Is this enough for me to repro the problems you were seeing with chromium's
> > clang?
> I think the following steps should reproduce the problem:
> 1.) Run: mkdir -p ~/.gyp && echo
> '{"variables":{"enable_coverage":1,"clang_xcode":0,}}' > ~/.gyp/include.gypi
&&
> gclient runhooks
> 2.) Compile ios_chrome_unittests target

Which command do I use to compile for the device? Which for the simulator?
(Sorry for the newbie questions!)

[commit-bot: I haz the power, 2015-01-24 00:47:27]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-24 00:48:34]

Patchset 1 (id:??) landed as
https://crrev.com/f24d6e272a97eab52bc27322e07d4160ece83408
Cr-Commit-Position: refs/heads/master@{#312983}

[Eugene But (OOO till 7-30), 2015-01-24 00:52:43]

On 2015/01/23 23:59:19, Nico wrote:
> On 2015/01/23 23:43:13, eugenebut wrote:
> > On 2015/01/23 21:38:15, Nico wrote:
> > > Every time you do something that spans more than 1 cl, please create a
> > tracking
> > > bug for that and reference it in all cls that are related to it (in this
> case,
> > > "coverage for chromium/ios", i suppose)
> > Updated the issue with our internal bug.
> > 
> > > Is this enough for me to repro the problems you were seeing with
chromium's
> > > clang?
> > I think the following steps should reproduce the problem:
> > 1.) Run: mkdir -p ~/.gyp && echo
> > '{"variables":{"enable_coverage":1,"clang_xcode":0,}}' > ~/.gyp/include.gypi
> &&
> > gclient runhooks
> > 2.) Compile ios_chrome_unittests target
> 
> Which command do I use to compile for the device? Which for the simulator?
> (Sorry for the newbie questions!)

Sorry, I don't build upstream code, but I believe the following commands should
work:
ninja -C out/Release-iphoneos All
ninja -C out/Release-iphonesimulator All