ios: Use a 10.7 deployment target for host builds.

iOS: Use a 10.7 deployment target for host builds.

The internal iOS build used to use libstdc++, but after
https://codereview.chromium.org/1334273004/ force libc+++ on for iOS the
internal bots broke because they use Xcode's clang and Xcode's clang
complains if -stdlib=libc++ is passed and the deployment target is not at
least 10.7.

As a fix, set the mac deployment target for iOS host compiles to 10.7, and
suppress warnings about deprecated functions for iOS host compiles.  (The
warnings can't be fixed until the deployment target is increased on Mac too;
this is covered by crbug.com/547071)

BUG=535104, 400091
Committed: https://crrev.com/469f0e325c36f278a9849051265f65cc2dcf804a
Cr-Commit-Position: refs/heads/master@{#355822}

[Nico, 2015-10-23 16:13:08]

Description was changed from

==========
iOS: Use a 10.7 deployment target for host builds.

The internal iOS build used to use libstdc++, but after
https://codereview.chromium.org/1334273004/ force libc+++ on for iOS the
internal bots broke because they use Xcode's clang and Xcode's clang
complains if -stdlib=libc++ is passed and the deployment target is not at
least 10.7.

As a fix, set the mac deployment target for iOS host compiles to 10.7, and
suppress warnings about deprecated functions for iOS host compiles.  (The
warnings can't be fixed until the deployment target is increased on Mac too;
this is covered by crbug.com/XXX)

BUG=535104,400091
==========

to

==========
iOS: Use a 10.7 deployment target for host builds.

The internal iOS build used to use libstdc++, but after
https://codereview.chromium.org/1334273004/ force libc+++ on for iOS the
internal bots broke because they use Xcode's clang and Xcode's clang
complains if -stdlib=libc++ is passed and the deployment target is not at
least 10.7.

As a fix, set the mac deployment target for iOS host compiles to 10.7, and
suppress warnings about deprecated functions for iOS host compiles.  (The
warnings can't be fixed until the deployment target is increased on Mac too;
this is covered by crbug.com/547071)

BUG=535104,400091
==========

[Nico, 2015-10-23 16:13:35]

thakis@chromium.org changed reviewers:
+ mark@chromium.org, sdefresne@chromium.org

[Nico, 2015-10-23 16:13:35]

This is the last piece of the puzzle.

[sdefresne, 2015-10-23 16:15:28]

lgtm

[Nico, 2015-10-23 16:15:56]

The CQ bit was checked by thakis@chromium.org

[commit-bot: I haz the power, 2015-10-23 16:16:56]

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

[Mark Mentovai, 2015-10-23 16:41:27]

LGTM

[commit-bot: I haz the power, 2015-10-23 17:59:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-10-23 18:00:53]

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

[Nico, 2015-10-27 18:25:20]

I filed http://crbug.com/548286 for porting this to gn (i tried to just do that,
but the gn/ios build is busted without any local changes, so i couldn't test my
patch, so i pasted it into a bug instead)