Fix GYP and GN references that are invalid in Chromium builds.

Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium builds:
- GN references between WebRTC targets must be using relative paths, not absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v variable
  in order to be expanded to the correct path in a Chromium build.

NOTRY=True
TBR=hjon@webrtc.org, hbos@webrtc.org

Committed: https://crrev.com/f6b55092295412a5cf1ffc7e77de0575eaca43b3
Cr-Commit-Position: refs/heads/master@{#11521}

[kjellander_webrtc, 2016-02-08 06:57:22]

Description was changed from

==========
Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium
builds:
- GN references between WebRTC targets must be using relative paths, not
absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v
variable
  in order to be expanded to the correct path in a Chromium build.
==========

to

==========
Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium
builds:
- GN references between WebRTC targets must be using relative paths, not
absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v
variable
  in order to be expanded to the correct path in a Chromium build.

TBR=hjon@webrtc.org, hbos@webrtc.org
==========

[kjellander_webrtc, 2016-02-08 06:57:23]

kjellander@webrtc.org changed reviewers:
+ hbos@webrtc.org, hjon@webrtc.org

[kjellander_webrtc, 2016-02-08 06:58:41]

I guess I should write PRESUBMIT checks for these oddities and/or get trybot
coverage for it (which I can actually setup once I'm done with
https://bugs.chromium.org/p/webrtc/issues/detail?id=4256).

[kjellander_webrtc, 2016-02-08 07:03:07]

Description was changed from

==========
Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium
builds:
- GN references between WebRTC targets must be using relative paths, not
absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v
variable
  in order to be expanded to the correct path in a Chromium build.

TBR=hjon@webrtc.org, hbos@webrtc.org
==========

to

==========
Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium
builds:
- GN references between WebRTC targets must be using relative paths, not
absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v
variable
  in order to be expanded to the correct path in a Chromium build.

NOTRY=True
TBR=hjon@webrtc.org, hbos@webrtc.org
==========

[kjellander_webrtc, 2016-02-08 07:03:12]

The CQ bit was checked by kjellander@webrtc.org

[commit-bot: I haz the power, 2016-02-08 07:03:22]

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

[commit-bot: I haz the power, 2016-02-08 07:04:30]

Description was changed from

==========
Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium
builds:
- GN references between WebRTC targets must be using relative paths, not
absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v
variable
  in order to be expanded to the correct path in a Chromium build.

NOTRY=True
TBR=hjon@webrtc.org, hbos@webrtc.org
==========

to

==========
Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium
builds:
- GN references between WebRTC targets must be using relative paths, not
absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v
variable
  in order to be expanded to the correct path in a Chromium build.

NOTRY=True
TBR=hjon@webrtc.org, hbos@webrtc.org
==========

[commit-bot: I haz the power, 2016-02-08 07:04:30]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-08 07:04:41]

Description was changed from

==========
Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium
builds:
- GN references between WebRTC targets must be using relative paths, not
absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v
variable
  in order to be expanded to the correct path in a Chromium build.

NOTRY=True
TBR=hjon@webrtc.org, hbos@webrtc.org
==========

to

==========
Fix GYP and GN references that are invalid in Chromium builds.

There were a couple of GN and GYP references that were incorrect in Chromium
builds:
- GN references between WebRTC targets must be using relative paths, not
absolute.
- GYP references between WebRTC targets must be using the <(webrtc_root)v
variable
  in order to be expanded to the correct path in a Chromium build.

NOTRY=True
TBR=hjon@webrtc.org, hbos@webrtc.org

Committed: https://crrev.com/f6b55092295412a5cf1ffc7e77de0575eaca43b3
Cr-Commit-Position: refs/heads/master@{#11521}
==========

[commit-bot: I haz the power, 2016-02-08 07:04:41]

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