title: Could not build Objective-C module, when using swift in objective-c module
body: <p>In an iOS application I have a subproject (not cocoapods) in which I have included a swift file and ObjC file (that is used by the swift file). XCode automatically created a bridging file but could not build it because apparantly bridging is not allowed in a framework. The workaround that I used was to add the objective-c header to the umbrella file and it worked. Now I need to use a swift class from ObjC. I have <code>define module</code> to set to YES, the generated file Framework-Swift.h . But when I try to import it in objective-c i get</p>
  
  <blockquote>
    <p>Could not build Objective-C module</p>
  </blockquote>
  
  <p>The closest I got after some googleing was this answer:</p>
  
  <blockquote>
    <p>Ah gotcha. It looks like you're building a mixed Swift &amp; Objective-C
    pod - if that's the case, Xcode will try to import
     within the generated -Swift.h header.
    You'll need to create the header manually and add imports for the
    Objective-C classes that you want to expose to Swift.</p>
    
    <p>CocoaPods generates an umbrella header automatically and imports it
    within the .modulemap, but Xcode doesn't use that when generating the
    -Swift.h header</p>
  </blockquote>
  
  <p>But I am unsure what header needs to be created manually. 
  Any ideeas or pointer about using swift in an objective-c framework ? In both ways ?</p>