Implement WebrtcTransport

remoting/remoting.gyp

 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 {
   'variables': {
 
     'branding_path': '../remoting/branding_<(branding)',
 
     'conditions': [
@@ skipping 219 matching lines @@
       'target_name': 'remoting_protocol',
       'type': 'static_library',
       'variables': { 'enable_wexit_time_destructors': 1, },
       'dependencies': [
         '../base/base.gyp:base',
         '../crypto/crypto.gyp:crypto',
         '../jingle/jingle.gyp:jingle_glue',
         '../net/net.gyp:net',
         '../third_party/expat/expat.gyp:expat',
         '../third_party/libjingle/libjingle.gyp:libjingle',
+        '../third_party/libjingle/libjingle.gyp:libjingle_webrtc',
+        '../third_party/libjingle/libjingle.gyp:libpeerconnection',

[halliwell, 2015/11/19 16:21:41]

This appears to be breaking builds where enable_webrtc == 0.

[Sergey Ulanov, 2015/11/19 19:28:21]

What's the reason you need to disable webrtc? Do you need to build remoting with
webrtc disabled? If not then you should also disable remoting: enable_remoting=0

[halliwell, 2015/11/20 04:44:45]

If you need to use targets that are guarded by enable_webrtc, you should use
that condition here too.  But I guess it got fixed already here
https://codereview.chromium.org/1457793004

         'remoting_base',
       ],
       'export_dependent_settings': [
         '../third_party/libjingle/libjingle.gyp:libjingle',
       ],
       'sources': [
         '<@(remoting_protocol_sources)',
         '<@(remoting_signaling_sources)',
       ],
     },  # end of target 'remoting_protocol'
   ],  # end of targets
 }