[NaCl SDK] Use gyp_nacl when building NaCl components via gyp

[NaCl SDK] Use gyp_nacl when building NaCl components via gyp

This fixes an the Mac SDK build which was failing due to
an incompatibility between chromium's chommon.gypi and
some of the untrusted targets in the NaCl tree.

Chromium's common.gypi was assuming all NaCl untrusted
targets define nacl_untrusted_build and adding libc++
headers to the include path for all non-nacl targets.
This was causing build failures since the libc++
headers are not compatible with the old version of gcc
used by NaCl.

CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_nacl_sdk;tryserver.chromium.mac:mac_nacl_sdk;tryserver.chromium.win:win_nacl_sdk

Committed: https://crrev.com/99c43acddde02a9cf9b2759ec80bca9983984a82
Cr-Commit-Position: refs/heads/master@{#356357}

[Sam Clegg, 2015-10-27 04:05:44]

Description was changed from

==========
[NaCl SDK] Use gyp_nacl when building NaCl components via gyp
==========

to

==========
[NaCl SDK] Use gyp_nacl when building NaCl components via gyp

gyp_chromium was having issues building untrusted targets
in native_client since they don't all define
nacl_untrusted_build and chromium's common.gyps was
assuming all NaCl untrusted targets define this and
adding libc++ headers to the include path for all non-nacl
targets.  This was causing build failures since the libc++
headers are not compatible with the old version of gcc
used by NaCl.
==========

[Sam Clegg, 2015-10-27 04:05:44]

sbc@chromium.org changed reviewers:
+ binji@chromium.org

[Sam Clegg, 2015-10-27 04:08:47]

Description was changed from

==========
[NaCl SDK] Use gyp_nacl when building NaCl components via gyp

gyp_chromium was having issues building untrusted targets
in native_client since they don't all define
nacl_untrusted_build and chromium's common.gyps was
assuming all NaCl untrusted targets define this and
adding libc++ headers to the include path for all non-nacl
targets.  This was causing build failures since the libc++
headers are not compatible with the old version of gcc
used by NaCl.
==========

to

==========
[NaCl SDK] Use gyp_nacl when building NaCl components via gyp

This fixes an the Mac SDK build which was failing due to
an incompatibility between chromium's chommon.gypi and
some of the untrusted targets in the NaCl tree.

Chromium's common.gypi was assuming all NaCl untrusted
targets define nacl_untrusted_build and adding libc++
headers to the include path for all non-nacl targets.
This was causing build failures since the libc++
headers are not compatible with the old version of gcc
used by NaCl.
==========

[Sam Clegg, 2015-10-27 04:09:25]

The CQ bit was checked by sbc@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-10-27 04:09:40]

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

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

The CQ bit was unchecked by commit-bot@chromium.org

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

Dry run: This issue passed the CQ dry run.

[binji, 2015-10-27 17:43:19]

lgtm

[Sam Clegg, 2015-10-27 18:55:03]

The CQ bit was checked by sbc@chromium.org

[commit-bot: I haz the power, 2015-10-27 18:56:12]

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

[commit-bot: I haz the power, 2015-10-27 19:05:32]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-10-27 19:06:03]

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