Exclude libjingle_peerconnection_{jni,so} targets from Chromium builds.

Exclude libjingle_peerconnection_{jni,so} targets from Chromium builds.

In GN, the libjingle_peerconnection_jni target becomes a part of
'all' implicitly, which surfaced the incompability between it
and the Chromium logging implementation. In the GYP build, the
target is not present due to api.gyp not being depended upon yet.

BUG=webrtc:4256
TBR=perkj@webrtc.org
NOTRY=True

Committed: https://crrev.com/69b34625c1ee2f527e481c420ff1294851463b77
Cr-Commit-Position: refs/heads/master@{#13231}

[kjellander_webrtc, 2016-06-21 07:30:28]

Description was changed from

==========
Exclude libjingle_peerconnection_{jni,so} targets from Chromium builds.

In GN, the libjingle_peerconnection_jni target becomes a part of
'all' implicitly, which surfaced the incompability between it
and the Chromium logging implementation. In the GYP build, the
target is not present due to api.gyp not being depended upon yet.

BUG=webrtc:4256
TBR=perkj@webrtc.org
==========

to

==========
Exclude libjingle_peerconnection_{jni,so} targets from Chromium builds.

In GN, the libjingle_peerconnection_jni target becomes a part of
'all' implicitly, which surfaced the incompability between it
and the Chromium logging implementation. In the GYP build, the
target is not present due to api.gyp not being depended upon yet.

BUG=webrtc:4256
TBR=perkj@webrtc.org
NOTRY=True
==========

[kjellander_webrtc, 2016-06-21 08:03:58]

The CQ bit was checked by kjellander@webrtc.org

[commit-bot: I haz the power, 2016-06-21 08:04:03]

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

[commit-bot: I haz the power, 2016-06-21 08:05:19]

Description was changed from

==========
Exclude libjingle_peerconnection_{jni,so} targets from Chromium builds.

In GN, the libjingle_peerconnection_jni target becomes a part of
'all' implicitly, which surfaced the incompability between it
and the Chromium logging implementation. In the GYP build, the
target is not present due to api.gyp not being depended upon yet.

BUG=webrtc:4256
TBR=perkj@webrtc.org
NOTRY=True
==========

to

==========
Exclude libjingle_peerconnection_{jni,so} targets from Chromium builds.

In GN, the libjingle_peerconnection_jni target becomes a part of
'all' implicitly, which surfaced the incompability between it
and the Chromium logging implementation. In the GYP build, the
target is not present due to api.gyp not being depended upon yet.

BUG=webrtc:4256
TBR=perkj@webrtc.org
NOTRY=True
==========

[commit-bot: I haz the power, 2016-06-21 08:05:20]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-21 08:05:27]

Description was changed from

==========
Exclude libjingle_peerconnection_{jni,so} targets from Chromium builds.

In GN, the libjingle_peerconnection_jni target becomes a part of
'all' implicitly, which surfaced the incompability between it
and the Chromium logging implementation. In the GYP build, the
target is not present due to api.gyp not being depended upon yet.

BUG=webrtc:4256
TBR=perkj@webrtc.org
NOTRY=True
==========

to

==========
Exclude libjingle_peerconnection_{jni,so} targets from Chromium builds.

In GN, the libjingle_peerconnection_jni target becomes a part of
'all' implicitly, which surfaced the incompability between it
and the Chromium logging implementation. In the GYP build, the
target is not present due to api.gyp not being depended upon yet.

BUG=webrtc:4256
TBR=perkj@webrtc.org
NOTRY=True

Committed: https://crrev.com/69b34625c1ee2f527e481c420ff1294851463b77
Cr-Commit-Position: refs/heads/master@{#13231}
==========

[commit-bot: I haz the power, 2016-06-21 08:05:28]

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