GN: Put BoringSSL Chromium specific targets inside a condition

GN: Put BoringSSL Chromium specific targets inside a condition

The boringssl_unittests target depends on Chromium's base,
so having it being processed by default results in errors
for other projects reusing the GN files for BoringSSL that
are located in the Chromium repo.

TBR=kjellander@chromium.org, davidben@chromium.org
BUG=webrtc:5829, 606944
Committed: https://crrev.com/1bbcf69d58af4e14e86019f59f75d669e2d2f65e
Cr-Commit-Position: refs/heads/master@{#389932}

[Dirk Pranke, 2016-04-26 21:51:03]

Description was changed from

==========
GN: Put BoringSSL Chromium specific targets inside a condition

The boringssl_unittests target depends on Chromium's base,
so having it being processed by default results in errors
for other projects reusing the GN files for BoringSSL that
are located in the Chromium repo.

BUG=webrtc:5829, 606944

patch from issue 1919383002 at patchset 60001
(http://crrev.com/1919383002#ps60001)
==========

to

==========
GN: Put BoringSSL Chromium specific targets inside a condition

The boringssl_unittests target depends on Chromium's base,
so having it being processed by default results in errors
for other projects reusing the GN files for BoringSSL that
are located in the Chromium repo.

TBR=kjellander@chromium.org, davidben@chromium.org
BUG=webrtc:5829, 606944
==========

[Dirk Pranke, 2016-04-26 21:51:03]

dpranke@chromium.org changed reviewers:
+ davidben@chromium.org, kjellander@chromium.org

[Dirk Pranke, 2016-04-26 21:51:27]

TBR'ing because of the approvals in 1919383002.

[Dirk Pranke, 2016-04-26 21:51:32]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2016-04-26 21:52:12]

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

[davidben, 2016-04-26 21:52:33]

lgtm

[commit-bot: I haz the power, 2016-04-26 22:46:39]

Description was changed from

==========
GN: Put BoringSSL Chromium specific targets inside a condition

The boringssl_unittests target depends on Chromium's base,
so having it being processed by default results in errors
for other projects reusing the GN files for BoringSSL that
are located in the Chromium repo.

TBR=kjellander@chromium.org, davidben@chromium.org
BUG=webrtc:5829, 606944
==========

to

==========
GN: Put BoringSSL Chromium specific targets inside a condition

The boringssl_unittests target depends on Chromium's base,
so having it being processed by default results in errors
for other projects reusing the GN files for BoringSSL that
are located in the Chromium repo.

TBR=kjellander@chromium.org, davidben@chromium.org
BUG=webrtc:5829, 606944
==========

[commit-bot: I haz the power, 2016-04-26 22:46:39]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-04-26 22:47:50]

Description was changed from

==========
GN: Put BoringSSL Chromium specific targets inside a condition

The boringssl_unittests target depends on Chromium's base,
so having it being processed by default results in errors
for other projects reusing the GN files for BoringSSL that
are located in the Chromium repo.

TBR=kjellander@chromium.org, davidben@chromium.org
BUG=webrtc:5829, 606944
==========

to

==========
GN: Put BoringSSL Chromium specific targets inside a condition

The boringssl_unittests target depends on Chromium's base,
so having it being processed by default results in errors
for other projects reusing the GN files for BoringSSL that
are located in the Chromium repo.

TBR=kjellander@chromium.org, davidben@chromium.org
BUG=webrtc:5829, 606944

Committed: https://crrev.com/1bbcf69d58af4e14e86019f59f75d669e2d2f65e
Cr-Commit-Position: refs/heads/master@{#389932}
==========

[commit-bot: I haz the power, 2016-04-26 22:47:51]

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

[kjellander_chromium, 2016-04-27 06:40:53]

lgtm, thanks!