Add WebRTC DEPS for Android builds.

Add WebRTC DEPS for Android builds.

This DEPS makes it possible to pull required additional
dependencies for Chromium that are needed to build
and execute WebRTC Android tests using Chromium's
Android test framework.

In addition to this deps solution, custom deps are needed
for src/third_party/webrtc in order to checkout the latest
code instead of the DEPS pinned revision of WebRTC stable
branch.

BUG=webrtc:2059
TEST=checked in the file in a local Subversion repo and tested
adding it as a separate solution, followed by a successful
gclient sync, with a .gclient configured for Android (see
https://code.google.com/p/chromium/wiki/AndroidBuildInstructions
for details).

R=hellner@google.com

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=211964

[kjellander_chromium, 2013-07-16 21:17:10]

Hi, using this DEPS file, we can avoid having these configuration details kept
in the buildbot config (which is cumbersome to update, especially as we want the
gflags dependency to go away in the future).

It shall be used by setting up a Chromium .gclient like this:
1. Add a custom_deps entry:
"src/third_party/webrtc": "http://webrtc.googlecode.com/svn/trunk/webrtc", 
2. Add an additional solution:
{ "name"        : "webrtc.DEPS",
    "url"         :
"svn:/​/​svn.chromium.org/​chrome/​trunk/​deps/​third_party/​webrtc/webrtc.DEPS",
  },
3. Run gclient sync

[hellner, 2013-07-17 02:06:06]

LGTM with one comment.

https://codereview.chromium.org/19235014/diff/2001/webrtc/webrtc.DEPS/DEPS
File webrtc/webrtc.DEPS/DEPS (right):

https://codereview.chromium.org/19235014/diff/2001/webrtc/webrtc.DEPS/DEPS#ne...
webrtc/webrtc.DEPS/DEPS:1: # DEPS file that pulls down dependencies that are
needed to build and
Do we need Chromium copyright header?

How are the DEPS dependencies being pulled down? I.e. who finds this file.

Is this usable to set up a Chromium workspace matching the waterfall.

I know you answer this in the cl description but I think it makes sense to
document it somewhere a developer can find it.

[hellner, 2013-07-17 02:06:07]

LGTM with one comment.

[kjellander_chromium, 2013-07-17 05:51:26]

Replied to your comments.
I will submit this now and start looking at configuring the buildbots.

https://codereview.chromium.org/19235014/diff/2001/webrtc/webrtc.DEPS/DEPS
File webrtc/webrtc.DEPS/DEPS (right):

https://codereview.chromium.org/19235014/diff/2001/webrtc/webrtc.DEPS/DEPS#ne...
webrtc/webrtc.DEPS/DEPS:1: # DEPS file that pulls down dependencies that are
needed to build and
On 2013/07/17 02:06:06, hellner wrote:
> Do we need Chromium copyright header?
Since Chrome doesn't have one in src/DEPS, I don't think so.

> How are the DEPS dependencies being pulled down? I.e. who finds this file.
The webrtc.DEPS directory is added as a solution in the .gclient spec, then the
contents of its DEPS file is pulled down just as regular dependencies.
I couldn't add src/third_party/webrtc in here though, since gclient then
complains about a conflict since it already exists in Chromium's src/DEPS.
Because of that, it had to be left out here and has to be configured in
custom_deps of the Chromium src/ solution instead.

> Is this usable to set up a Chromium workspace matching the waterfall.
Yes, this is usable for everyone that wants to setup a Chromium workspace to
build and run WebRTC Android tests with it, including the bots. 
The advantage of this approach compared to the one you suggested in
https://code.google.com/p/webrtc/issues/detail?id=1882 is that if the
dependencies change, we just update webrtc.DEPS/DEPS and don't have to
communicate the changes. That approach also didn't pin the revision for
google-gflags, which we should.

> I know you answer this in the cl description but I think it makes sense to
> document it somewhere a developer can find it.
Yes, we should replace the documentation in
https://code.google.com/p/webrtc/issues/detail?id=1882 or the future public
webrtc.org page, with this as soon we've confirmed it works as intended.

[kjellander_chromium, 2013-07-17 05:52:10]

Committed patchset #1 manually as r211964 (presubmit successful).