Move talk/examples/* to webrtc/examples.

Move all the examples from the talk directory into the webrtc examples directory.

Significant changes:

- move the libjingle_examples.gyp file into webrtc directory.
- rename talk/examples/android to webrtc/examples/androidapp to avoid name conflicts.
- update paths in talk/libjingle_tests.gyp to point to webrtc directory for Objective-C test.

BUG=
R=pthatcher@webrtc.org, tkchin@webrtc.org

Committed: https://chromium.googlesource.com/external/webrtc/+/a8736448970fedd82f051c6b2cc89185b755ddf3

[decurtis_webrtc, 2015-07-14 21:09:39]

The CQ bit was checked by decurtis@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2015-07-14 21:09:58]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1235563006/20001

[commit-bot: I haz the power, 2015-07-14 21:14:06]

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

[commit-bot: I haz the power, 2015-07-14 21:14:08]

Dry run: Try jobs failed on following builders:
  ios_arm64_rel on tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/ios_arm64_rel/builds/3354)

(exceeded global retry quota)

[decurtis_webrtc, 2015-07-14 23:43:37]

The CQ bit was checked by decurtis@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2015-07-14 23:43:53]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1235563006/30001

[commit-bot: I haz the power, 2015-07-14 23:49:12]

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

[commit-bot: I haz the power, 2015-07-14 23:49:14]

Dry run: Try jobs failed on following builders:
  presubmit on tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/presubmit/builds/177)

[decurtis_webrtc, 2015-07-15 20:19:04]

decurtis@webrtc.org changed reviewers:
+ pthatcher@webrtc.org

[decurtis_webrtc, 2015-07-15 20:25:10]

I compiled this change against chromium with no issues.

[pthatcher1, 2015-07-16 05:28:27]

lgtm

[decurtis_webrtc, 2015-07-16 17:36:02]

decurtis@webrtc.org changed reviewers:
+ tkchin@webrtc.org

[decurtis_webrtc, 2015-07-16 17:36:20]

Add ZEKE for LGTM on examples move.

[tkchin_webrtc, 2015-07-22 21:07:55]

On 2015/07/16 17:36:20, decurtis_webrtc wrote:
> Add ZEKE for LGTM on examples move.

Sorry, missed this.
lgtm (but might need to sync + check copyright conversion issue)

[tkchin_webrtc, 2015-07-22 21:08:21]

https://codereview.webrtc.org/1235563006/diff/30001/webrtc/libjingle_examples...
File webrtc/libjingle_examples.gyp (right):

https://codereview.webrtc.org/1235563006/diff/30001/webrtc/libjingle_examples...
webrtc/libjingle_examples.gyp:2: # Copyright 2012 The WebRTC Project Authors.
All rights reserved.
I don't think we're allowed to change copyright notices. Please check.

[Andrew MacDonald, 2015-07-22 22:06:46]

andrew@webrtc.org changed reviewers:
+ andrew@webrtc.org

[Andrew MacDonald, 2015-07-22 22:06:49]

https://codereview.webrtc.org/1235563006/diff/30001/webrtc/libjingle_examples...
File webrtc/libjingle_examples.gyp (right):

https://codereview.webrtc.org/1235563006/diff/30001/webrtc/libjingle_examples...
webrtc/libjingle_examples.gyp:2: # Copyright 2012 The WebRTC Project Authors.
All rights reserved.
On 2015/07/22 21:08:21, tkchin_webrtc wrote:
> I don't think we're allowed to change copyright notices. Please check.

In any case, you definitely shouldn't mix license text like this.

I believe replacing the libjingle with webrtc license is fine, since Google
holds the copyright, but you could confirm with e.g. dannyb@.

[decurtis_webrtc, 2015-07-27 17:24:18]

https://codereview.webrtc.org/1235563006/diff/30001/webrtc/libjingle_examples...
File webrtc/libjingle_examples.gyp (right):

https://codereview.webrtc.org/1235563006/diff/30001/webrtc/libjingle_examples...
webrtc/libjingle_examples.gyp:2: # Copyright 2012 The WebRTC Project Authors.
All rights reserved.
On 2015/07/22 22:06:49, andrew wrote:
> On 2015/07/22 21:08:21, tkchin_webrtc wrote:
> > I don't think we're allowed to change copyright notices. Please check.
> 
> In any case, you definitely shouldn't mix license text like this.
> 
> I believe replacing the libjingle with webrtc license is fine, since Google
> holds the copyright, but you could confirm with e.g. dannyb@.

Done.

[decurtis_webrtc, 2015-07-27 17:25:27]

OK. I think this is good to go. If you want to have any last look please do
before tomorrow. 

I went through and painstakingly verified each license now and the presubmit
check should actually catch anything that is off but maybe doesn't check GYP
files.

[niklas.enbom, 2015-08-05 22:33:40]

all.gyp lgtm
On 2015/07/27 17:25:27, decurtis_webrtc wrote:
> OK. I think this is good to go. If you want to have any last look please do
> before tomorrow. 
> 
> I went through and painstakingly verified each license now and the presubmit
> check should actually catch anything that is off but maybe doesn't check GYP
> files.

[decurtis_webrtc, 2015-08-05 22:48:42]

Committed patchset #6 (id:50001) manually as
a8736448970fedd82f051c6b2cc89185b755ddf3 (presubmit successful).

[brucedawson, 2015-08-11 21:49:46]

It looks like this change left some dangling references in libjingle.gyp. When
rebuilding Chromium's ninja files with GYP_GENERATORS=ninja,msvs-ninja these
warnings appear:

Warning: Missing input files:
D:\src\chromium\src\third_party\libjingle\source\talk\examples\peerconnection\server\peer_channel.h
D:\src\chromium\src\third_party\libjingle\source\talk\examples\peerconnection\server\data_socket.cc
D:\src\chromium\src\third_party\libjingle\source\talk\examples\peerconnection\server\utils.cc
D:\src\chromium\src\third_party\libjingle\source\talk\examples\peerconnection\server\utils.h
D:\src\chromium\src\third_party\libjingle\source\talk\examples\peerconnection\server\data_socket.h
D:\src\chromium\src\third_party\libjingle\source\talk\examples\peerconnection\server\main.cc
D:\src\chromium\src\third_party\libjingle\source\talk\examples\peerconnection\server\peer_channel.cc

These files constitute all of the inputs to the peerconnection_server target.
This target should either be deleted or updated, to avoid future confusion.