title: Using a CocoaPod dependency while developing a CocoaPod
body: <p>I'm creating a CocoaPod, say <code>MyPod</code>, which depends on another Cocoapod, say <code>RxSwift</code>.</p>
  
  <p>So I have this in <code>MyPod.podspec</code>:</p>
  
  <pre><code>s.dependency "RxSwift", "~&gt; 3.0.1"
  </code></pre>
  
  <p>However, while developing <code>MyPod</code>, how can I actually use the dependency?</p>
  
  <pre><code>import RxSwift
  //     ^
  // No such module 'RxSwift'
  
  public class MyClass { //...
  </code></pre>
  
  <p>Is there a step I'm missing, or some common convention?  It looks like some other projects like <a href="https://github.com/Moya/Moya" rel="noreferrer">Moya</a> are using <a href="https://github.com/Carthage/Carthage" rel="noreferrer">Carthage</a> to build dependencies while developing. Should I be doing that, or maybe adding a <code>Podfile</code>?</p>
  
  <p>I know that this shouldn't be a problem for an Example App located within the repo, which would have its own <code>Podfile</code>.  However, I'd like to still have tests located at top level, outside of the Example App, and to be able to actually build the framework while working on it, again, outside of an Example App.</p>