Re-land: "Use an explicit identifier in Config"

Re-land: "Use an explicit identifier in Config"

This let's us use them to configure them when using WebRTC as an external library. One use case where this is necessary is in the Android OS.

Original CL: https://codereview.webrtc.org/1538643004/

TBR=tommi@webrtc.org

Committed: https://crrev.com/688e308a353c27803a66803230235638f4dd1f2b
Cr-Commit-Position: refs/heads/master@{#11248}

[aluebs-webrtc, 2016-01-13 23:49:15]

Fixed error in Chrome and re-landing this.

[aluebs-webrtc, 2016-01-13 23:49:20]

The CQ bit was checked by aluebs@webrtc.org

[commit-bot: I haz the power, 2016-01-13 23:49:33]

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

[commit-bot: I haz the power, 2016-01-14 01:35:34]

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

[commit-bot: I haz the power, 2016-01-14 01:35:34]

Try jobs failed on following builders:
  linux_libfuzzer_rel on tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/linux_libfuzzer_rel/bui...)

[aluebs-google, 2016-01-14 01:37:02]

The CQ bit was checked by aluebs@google.com

[commit-bot: I haz the power, 2016-01-14 01:37:10]

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

[commit-bot: I haz the power, 2016-01-14 01:49:54]

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

[commit-bot: I haz the power, 2016-01-14 01:49:54]

Try jobs failed on following builders:
  android_arm64_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL)
  linux_baremetal on tryserver.webrtc (JOB_TIMED_OUT, no build URL)
  win_baremetal on tryserver.webrtc (JOB_TIMED_OUT, no build URL)

[aluebs-webrtc, 2016-01-14 01:52:22]

The CQ bit was checked by aluebs@webrtc.org

[commit-bot: I haz the power, 2016-01-14 01:52:30]

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

[commit-bot: I haz the power, 2016-01-14 02:57:34]

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

[commit-bot: I haz the power, 2016-01-14 02:57:35]

Try jobs failed on following builders:
  linux_libfuzzer_rel on tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/linux_libfuzzer_rel/bui...)

[tommi, 2016-01-14 12:31:08]

The CQ bit was checked by tommi@webrtc.org

[tommi, 2016-01-14 12:31:09]

lgtm

[commit-bot: I haz the power, 2016-01-14 12:31:47]

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

[commit-bot: I haz the power, 2016-01-14 12:32:49]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-01-14 12:32:55]

Description was changed from

==========
Re-land: "Use an explicit identifier in Config"

This let's us use them to configure them when using WebRTC as an external
library. One use case where this is necessary is in the Android OS.

Original CL: https://codereview.webrtc.org/1538643004/

TBR=tommi@webrtc.org
==========

to

==========
Re-land: "Use an explicit identifier in Config"

This let's us use them to configure them when using WebRTC as an external
library. One use case where this is necessary is in the Android OS.

Original CL: https://codereview.webrtc.org/1538643004/

TBR=tommi@webrtc.org

Committed: https://crrev.com/688e308a353c27803a66803230235638f4dd1f2b
Cr-Commit-Position: refs/heads/master@{#11248}
==========

[commit-bot: I haz the power, 2016-01-14 12:32:56]

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