StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In the past months, I've learned a lot more about frameworks, so I'm rewriting this answer. Please note that I'm talking about <strong>installing a framework as part of the development workflow</strong>.</p> <p>The preferred location for installing a public framework (i.e. a framework that will be used by more than one of your apps or bundles) is /Library/Frameworks[link text] because "frameworks in this location are discovered automatically by the compiler at compile time and the dynamic linker at runtime."[Framework Programming Guide]. The most elegant way to do this is in the Deployment section of the Build settings.</p> <p>As you work on your framework, there are times when you do want to update the framework when you do a build, and times when you don't. For that reason, I change the Deployment settings only in the Release Configuration. So:</p> <ol> <li>Double-click on the framework target to bring up the Target info window and switch to the Build tab. </li> <li>Select Release in the Configuration selectbox. </li> <li>Scroll down to the Deployment section and enter the following values:</li> </ol> <blockquote> <p>Deployment Location = YES (click the checkbox)</p> <p>Installation Build Products Location = /</p> <p>Installation Directory = /Library/Frameworks</p> </blockquote> <p>The Installation Build Products Location serves as the root of the installation. Its default value is some /tmp directory: if you don't change it to the system root, you'll never see your installed framework since it's hiding in the /tmp.</p> <p>Now you can work on your framework as you like in the Debug configuration without upsetting your other projects and when you are ready to publish all you need to do is switch to Release and do a Build.</p> <p><strong>Xcode 4 Warning</strong> Since switching to Xcode 4, I've experienced a number of problems with my custom framework. Mostly, they are linking warnings in GDB that do not really interfere with the usefulness of the framework, except when running the built-in unit-test. I have submitted a technical support ticket to Apple a week ago, and they are still looking into it. When I get a working solution I will update this answer since the question has proven quite popular (1 kViews and counting).</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload