title: Use Cocoapods with an App Extension
body: <p>I'm trying to build a photo App Extension in Xcode 6 Beta-6 that uses cocoapods libraries.
  The bridging header that Xcode creates for the photo extension can't see anything from cocoapods.</p>
  
  <p>For example: <code>#import &lt;GPUImage/GPUImage.h&gt;</code> results in the error <code>"GPUImage/GPUImage.h" file not found</code>.</p>
  
  <p>I've tried every conceivable path for the import (with brackets and quotes) and have had almost no success.  The exception is that for simple pods like <code>SVProgressHUD</code>, the following ugly terrible hack works:
  <code>#import "../Pods/SVProgressHUD/SVProgressHUD/SVProgressHUD.h"</code>.</p>
  
  <p>But for GPUImage, it walks into the <code>GPUImage.h</code> header and decides it suddenly can't see <code>GPUImageContext.h</code> despite having no issue when this is imported with the bridging header for the normal swift code that is not part of the app extension.</p>
  
  <p>What is different about the compilation of app extensions that is preventing the bridging header from behaving sanely?</p>
  
  <p>Note:
  I've read every possible permutation of <a href="https://medium.com/@stigi/swift-cocoapods-da09d8ba6dd2" rel="noreferrer">this tutorial</a> and it is not immediately applicable, just in case anyone thinks they have found the answer there.</p>
  
  <p>Also, the problem described in <a href="https://stackoverflow.com/q/25495225/579405">this SO question</a> may be related, but I asked this question anyway in case my issue is specific to app extensions.  </p>