nacl: Be more consistent about setting nacl_untrusted_build on targets that use untrusted.gypi

nacl: Be more consistent about setting nacl_untrusted_build on targets that use untrusted.gypi

The motivation is that I want to add a certain include_dir to all targets (to
use libc++ on OS X), _except_ for NaCl targets, since these have their own
bundled C++ standard library already.  Checking for nacl_untrusted_build almost
works, but a handful nacl targets didn't set that yet.  Fix this.  No intended
behavior change.

BUG=400091
Committed: https://crrev.com/cdde1a7e0f809dd3b368e5f8c48292bafdba9808
Cr-Commit-Position: refs/heads/master@{#348815}

[Nico, 2015-09-15 01:00:45]

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

[Nico, 2015-09-15 01:01:20]

https://codereview.chromium.org/1332163005/diff/1/ppapi/ppapi_nacl_test_commo...
File ppapi/ppapi_nacl_test_common.gypi (right):

https://codereview.chromium.org/1332163005/diff/1/ppapi/ppapi_nacl_test_commo...
ppapi/ppapi_nacl_test_common.gypi:17: 'nacl_untrusted_build': 1,
(seems like every target including this gypi probably wants this)

[bradnelson, 2015-09-15 01:25:16]

lgtm

https://codereview.chromium.org/1332163005/diff/1/ppapi/ppapi_nacl_test_commo...
File ppapi/ppapi_nacl_test_common.gypi (right):

https://codereview.chromium.org/1332163005/diff/1/ppapi/ppapi_nacl_test_commo...
ppapi/ppapi_nacl_test_common.gypi:17: 'nacl_untrusted_build': 1,
On 2015/09/15 01:01:20, Nico wrote:
> (seems like every target including this gypi probably wants this)


Not sure. There may be places where not every target in a file in a nacl one.

[Nico, 2015-09-15 01:28:12]

The CQ bit was checked by thakis@chromium.org

[commit-bot: I haz the power, 2015-09-15 01:28:22]

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

[Nico, 2015-09-15 01:28:33]

On 2015/09/15 01:25:16, bradnelson wrote:
> lgtm
> 
>
https://codereview.chromium.org/1332163005/diff/1/ppapi/ppapi_nacl_test_commo...
> File ppapi/ppapi_nacl_test_common.gypi (right):
> 
>
https://codereview.chromium.org/1332163005/diff/1/ppapi/ppapi_nacl_test_commo...
> ppapi/ppapi_nacl_test_common.gypi:17: 'nacl_untrusted_build': 1,
> On 2015/09/15 01:01:20, Nico wrote:
> > (seems like every target including this gypi probably wants this)
> 
> 
> Not sure. There may be places where not every target in a file in a nacl one.

At the moment, all targets using this gypi seem to be nacl targets from what I
can tell.

[commit-bot: I haz the power, 2015-09-15 01:39:40]

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

[commit-bot: I haz the power, 2015-09-15 01:39:41]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Nico, 2015-09-15 01:49:45]

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

[Nico, 2015-09-15 01:49:45]

raymes: ppapi/OWNERS stamp, please

[Nico, 2015-09-15 01:50:07]

The CQ bit was checked by thakis@chromium.org

[commit-bot: I haz the power, 2015-09-15 01:50:12]

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

[raymes, 2015-09-15 01:52:55]

rubberstamp lgtm

[commit-bot: I haz the power, 2015-09-15 01:57:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-15 01:58:12]

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

[commit-bot: I haz the power, 2015-09-23 12:41:24]

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