Add implementation and tests for RTCIceServer

webrtc/api/api.gyp

Index: webrtc/api/api.gyp
diff --git a/webrtc/api/api.gyp b/webrtc/api/api.gyp
new file mode 100644
index 0000000000000000000000000000000000000000..5c6cd0df63eb6e08f707c967f3f7827051476eaf
--- /dev/null
+++ b/webrtc/api/api.gyp
@@ -0,0 +1,34 @@
+# Copyright (c) 2015 The WebRTC project authors. All Rights Reserved.
+#
+# Use of this source code is governed by a BSD-style license
+# that can be found in the LICENSE file in the root of the source
+# tree. An additional intellectual property rights grant can be found
+# in the file PATENTS.  All contributing project authors may
+# be found in the AUTHORS file in the root of the source tree.
+
+{
+  'includes': [ '../build/common.gypi', ],
+  'conditions': [
+    ['OS=="ios"', {
+      'targets': [
+        {
+          'target_name': 'rtc_api_objc',

[pthatcher1, 2015/12/11 01:51:49]

Would just rtc_obj make more sense as a top-level target?

[tkchin_webrtc, 2015/12/14 02:57:45]

Presumably the PeerConnection bits are going to be rtc_api similar to rtc_base
etc. So a objc suffix seems to make sense. We can change it later if we want.
There won't be a top level target for everything objc in general.

+          'type': 'static_library',
+          'dependencies': [
+            '<(webrtc_root)/base/base.gyp:rtc_base_objc',
+          ],
+          'sources': [
+            'objc/RTCIceServer+Private.h',
+            'objc/RTCIceServer.h',
+            'objc/RTCIceServer.mm',
+          ],
+          'xcode_settings': {
+            'CLANG_ENABLE_OBJC_ARC': 'YES',
+            'CLANG_WARN_OBJC_MISSING_PROPERTY_SYNTHESIS': 'YES',
+            'GCC_PREFIX_HEADER': 'objc/WebRTC-Prefix.pch',
+          },
+        }
+      ],
+    }], # OS=="ios"
+  ],
+}