Archive for Xcode

Framework versioning

Because I always forget how to do Framework versioning, I thought I’d link to Apple’s Framework Versioning Guidelines. The key points are:

If you change the interface: You must change the major version designator for your project. Build your framework and incorporate the new version into your existing framework directory structure.

If you extend the interface: Increment your current version number and set your compatibility version number to match. Build your framework.

If you make a change that does not change the interface: Increment your current version number. Do not change the compatibility version number.

I’ll now proceed to promptly forget all about making this post, too, I wager. I’ll probably find it again 30 minutes into hunting the net for how to do Framework versioning again in the future.

Leave a Comment

File templates in Xcode 3

Xcode 3 changed the locations in which it is looking for custom file templates. These must now be in ~/Library/Application Support/Developer/Shared/Xcode/File Templates/. Start by copying the default ones from /Developer/Library/Xcode/File Templates/, then edit them to your heart’s content.

Why would you bother having custom templates? One reason might be because you want to automatically fill your headers and source files with a copyright header. Or maybe you find the default comment a bit wordy and would like to shorten it. Here’s the one I’ve just created for Unit test classes, for example:

//
//  Copyright (c) «YEAR» «FULLUSERNAME». All rights reserved.
//

For the record: Xcode 2.x looked in ~/Library/Application Support/Apple/Developer Tools/File Templates/, as detailed in a previous post.

Leave a Comment

Follow

Get every new post delivered to your Inbox.