title: How does Xcode find implicit target dependencies?
body: <p>Xcode finds dependencies automatically sometimes. I think is is ok when I am the one who is defining the relationships and when I get lazy ... </p>
  
  <p>But more than often I find myself facing an existent (medium to large size) project with several targets. Since the project has been made by someone else I find it very difficult to understand what targets depends on what since <em>not all the relationships are explicit</em>.</p>
  
  <p><strong>What are the rules Xcode use to find such relationships?</strong> ( I hope I can understand the logic so <em>run</em> it in my mind and maybe save me some time in the future) Or <strong>What makes a target qualifiable to be implicitly dependant of another?</strong></p>
  
  <blockquote>
    <p>A target and the product it creates can be related to another target. If a target requires the output of another target in order to build, the first target is said to depend upon the second. If both targets are in the same workspace, Xcode can discover the dependency, in which case it builds the products in the required order. Such a relationship is referred to as an implicit dependency. </p>
  </blockquote>
  
  <p>Source: <a href="https://developer.apple.com/library/ios/featuredarticles/XcodeConcepts/Concept-Targets.html" rel="noreferrer">iOS Developer Library → Xcode Concepts → Xcode Target</a></p>