On 25/06/2010, at 7:52 AM, Chris Tracewell wrote: > Obviously, I have a setting wrong somewhere as it is seeing an older version > of the framework than I am linking to. Any thoughts where I should look?
If the problem is that it can't see a certain class in the framework, have you made sure that the header for that class has its role set to 'Public'? That causes it to get copied into the framework's headers directory that your client code should be looking for. The other thing you should do if the framework is embedded in the app is to set both the framework and app to build to the same directory. The documentation on embedding frameworks explains how. What you want to avoid is your framework ending up in ~/Library/Frameworks or /Library/Frameworks so check those places for old versions. --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
