title: .c File via Bridging Header Not Working After Xcode 8 Update
body: <p>The app I've been working on uses an external library, pdlib, which has it's own externals (.c files) which I've been importing via the bridging header <code>#import "Uzi.c"</code> and calling in my main Swift file via Uzi.c's setup function <code>Uzi_setup()</code> in my <code>ViewController</code> class.  I've had no problem with this until after updating to new public Xcode 8 a few days ago (I had no problem with Xcode 8 Beta 1 over the Summer).  </p>
  
  <p>Here are the 7 errors I get, listed under a single "Mach-O Linker Error" umbrella:</p>
  
  <pre><code>Undefined symbols for architecture x86_64:
  "_Uzi_bang", referenced from:
    _Uzi_setup in ViewController.o
  "_Uzi_class", referenced from:
    _Uzi_setup in ViewController.o
  "_Uzi_float", referenced from:
    _Uzi_setup in ViewController.o
  "_Uzi_new", referenced from:
    _Uzi_setup in ViewController.o
  "_Uzi_pause", referenced from:
    _Uzi_setup in ViewController.o
  "_Uzi_resume", referenced from:
    _Uzi_setup in ViewController.o
  ld: symbol(s) not found for architecture x86_64
  clang: error: linker command failed with exit code 1 (use -v to see invocation)
  </code></pre>
  
  <p>Those undefined symbols are 6 functions and a class declare from Uzi.c.  Here's a link to the whole c file: <a href="https://github.com/electrickery/pd-miXedSon/blob/master/hammer/Uzi.c" rel="nofollow">https://github.com/electrickery/pd-miXedSon/blob/master/hammer/Uzi.c</a></p>
  
  <p>I've tried every solution I've found online for dealing with similar problems, with no solution yet... I tried changing the "Architecture" and "Valid Architecture" settings to only armv7 and armv7s (no arm64) and changed "Build Active Architecture Only" to "No".  These step seem to help others in similar situations, but they didn't work for me (and taking away arm64 causes additional errors to appear).</p>
  
  <p>XCode 8 is pretty recent (the public version was released Sept. 13), so there are virtually no other questions about this upgrade causing a similar problem.  </p>
  
  <p>Any help would be greatly appreciated!</p>