title: GVRSDK iOS Xcode linker error
body: <p>I'm trying to create a GVRCardboardView in my iOS app written in Xcode 8.2, Swift 3.0. I have a GVRVideoView running but can't get the app to compile when adding with the GVRCardboardView. I am using a Bridging-Header to gain access to the Objective C files for the the cardboard SDK.</p>
  
  <p>This is the header file:</p>
  
  <pre><code>#ifndef Bridging_Header_h
  #define Bridging_Header_h
  
  #import "GVRWidgetView.h"
  #import "GVRPanoramaView.h"
  #import "GVROverlayView.h"
  #import "GVRVideoView.h"
  #import "GVRHeadTransform.h"
  #import "GVRCardboardView.h"
  #import "GVRAudioEngine.h"
  
  #endif
  </code></pre>
  
  <p>And the resulting error when compiling...</p>
  
  <pre><code>ld: library not found for -lGVRView_arm
  clang: error: linker command failed with exit code 1 (use -v to see invocation)
  </code></pre>
  
  <p>If I change my Podfile from: (reference @ <a href="https://github.com/googlevr/gvr-ios-sdk/blob/master/Samples/TreasureHunt/Podfile" rel="nofollow noreferrer">https://github.com/googlevr/gvr-ios-sdk/blob/master/Samples/TreasureHunt/Podfile</a>)</p>
  
  <pre><code>target 'My App Name' do
      pod 'GVRSDK/SDK'
  end
  </code></pre>
  
  <p>to:</p>
  
  <pre><code>target 'My App Name' do
      pod 'GVRSDK'
  end
  </code></pre>
  
  <p>Then the resulting error changes to: </p>
  
  <pre><code>Undefined symbols for architecture armv7:
  "_OBJC_CLASS_$_GVRCardboardView", referenced from:
    objc-class-ref in MyGVRViewController.o
  ld: symbol(s) not found for architecture armv7
  clang: error: linker command failed with exit code 1 (use -v to see invocation)
  </code></pre>
  
  <p>It seems now the app can find the -lGVRView_arm code but now isn't properly linking to the GVRCardboardView objective C class.</p>
  
  <p>What am I missing? Why won't my app compile?</p>
  
  <p>--EDIT--</p>
  
  <p>As the error stated that there is an undefined symbol for architecture <strong>armv7</strong>, I tried a newer device with <strong>arm64</strong>. I still receive a similar error.</p>