title: Public Header Path, Installation Directory, Search Header Path and other nightmares
body: <p>I have a project composed of 2 libraries (libraryA and libraryB) and a bundle. Each one of these were created like a project and imported on the main project by dragging them.</p>
  
  <p>Just dragging them were not enough for Xcode to find all headers to compile the whole project, so I had to hack the paths using hard ones but this is bad because paths can change and I will not be able to compile this project again. I want to use macros like <a href="http://developer.apple.com/library/mac/#documentation/DeveloperTools/Reference/XcodeBuildSettingRef/1-Build_Setting_Reference/build_setting_ref.html" rel="nofollow">these ones</a> to access the files, but after testing almost all of them, I was not able to make it work.</p>
  
  <p>The solution I have to make the compilation work is the following.</p>
  
  <p>I have adjusted each library in a way that their public headers are saved inside</p>
  
  <pre><code>/Users/rubberduck/Library/Developer/Xcode/DerivedData/MyProject-dnaimaovsccuvieahmvgttwjnabc/Build/Products/Debug-iphoneos/
  </code></pre>
  
  <p>using target names, so after they compile they will put their public headers on</p>
  
  <pre><code>/Users/rubberduck/Library/Developer/Xcode/DerivedData/MyProject-dnaimaovsccuvieahmvgttwjnabc/Build/Products/Debug-iphoneos/libraryA
  </code></pre>
  
  <p>and </p>
  
  <pre><code>/Users/rubberduck/Library/Developer/Xcode/DerivedData/MyProject-dnaimaovsccuvieahmvgttwjnabc/Build/Products/Debug-iphoneos/libraryB
  </code></pre>
  
  <p>The problem now is that libraryB needs libraryA's headers to compile. If these are siblings directories what should I put on libraryB's headers search path to point to libraryA's.</p>
  
  <p>NOTE: I need a path that is not hardcoded but rather using one of those macros I have mentioned.</p>