title: Best way to install a custom cocoa framework
body: <p>I have a custom framework that, following the advice in Apple's Framework Programming Guide >> <a href="http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPFrameworks/Tasks/InstallingFrameworks.html#//apple_ref/doc/uid/20002261" rel="noreferrer">Installing your framework</a> I install in /Library/Frameworks. I do this by adding a Run Script build phase with the following script:</p>
  
  <pre><code>cp -R  build/Debug/MyFramework.framework /Library/Frameworks
  </code></pre>
  
  <p>In my projects I then link against /Library/Frameworks/MyFramework and import it in my classes like so:</p>
  
  <pre><code>#import &lt;MyFramework/MyFramework.h&gt;
  </code></pre>
  
  <p>This works very well, except that I always see the following message in my debugger console:</p>
  
  <blockquote>
    <p>Loading program into debugger…
    sharedlibrary apply-load-rules all
    warning: Unable to read symbols for "/Users/elisevanlooij/Library/Frameworks/MyFramework.framework/Versions/A/MyFramework" (file not found).
    warning: Unable to read symbols from "MyFramework" (not yet mapped into memory).
    Program loaded.</p>
  </blockquote>
  
  <p>Apparently, the compiler first looks in /Users/elisevanlooij/Library/Frameworks, can't find MyFramework, then looks in /Library/Frameworks, does find MyFramework and continues on its merry way. So far this has been more of an annoyance than a real problem, but when runnning unit tests, gdb stops on the (file not found) and refuses to continue. I have solved the problem by adding an extra line to the Run Script Phase</p>
  
  <pre><code>cp -R  build/Debug/MyFramework.framework ~/Library/Frameworks
  </code></pre>
  
  <p>but it feels like sello-taping something that shouldn't be broken in the first place. How can I fix this?</p>