On Jun 24, 2010, at 6:59 PM, Graham Cox wrote: > > 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 > > >
Thanks Graham - I had made the headers all public. Also, I had the frameworks build directory set to @executable_path/../Frameworks. I did take your advice and checked /Library/Frameworks and ~/Library/Frameworks but neither had them there. I did get it working however, kind of by accident - I renamed the enclosing directory that houses all of the different versions of the framework which caused me to have to re-embed the framework into the linking app, like I had done a million times before trying to get this to work, an wallah, everything works. It sounds crazy, but somewhere there had to be a cached reference or setting that was causing it to stick with the previous fw version - even after cleaning and building and re-linking to the correct fw version over and over. Maybe I'm crazy. (likely) --Chris_______________________________________________ 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
