The peerconnection_server built target now depends on the libjingle.

third_party/libjingle/libjingle.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.
 
 {
   'includes': [
     '../../build/win_precompile.gypi',
   ],
   'target_defaults': {
     'defines': [
@@ skipping 629 matching lines @@
         'source/talk/examples/peerconnection/server/data_socket.h',
         'source/talk/examples/peerconnection/server/main.cc',
         'source/talk/examples/peerconnection/server/peer_channel.cc',
         'source/talk/examples/peerconnection/server/peer_channel.h',
         'source/talk/examples/peerconnection/server/utils.cc',
         'source/talk/examples/peerconnection/server/utils.h',
       ],
       'include_dirs': [
         'source',
       ],
+      'dependencies': [
+        'libjingle',

[Sergey Ulanov, 2012/07/31 17:47:25]

How did it work previously, without this dependency?
don't you also need libjingle_peerconnection?

[Ronghua Wu (Left Chromium), 2012/07/31 17:51:25]

The peerconnection_server is basically a socket application which relays the
signaling. Recently we added support of command line flags to it, which uses
some code from the libjingle base.

This is used by our pyauto tests, which is not part of the chromium build. 

+      ],
     }, # target peerconnection_server
   ],
 }