Xcode 4 DerivedData folder and Framework Search Paths
Xcode 4 DerivedData folder and Framework Search Paths
- Subject: Xcode 4 DerivedData folder and Framework Search Paths
- From: Bill Cheeseman <email@hidden>
- Date: Thu, 30 Jun 2011 08:15:53 -0400
My product's Xcode 4 workspace includes an application project and a framework project. My product uses the Xcode 4 default preference setting to place all built products in the new Xcode 4 DerivedData folder.
When I make a change to the framework's source code in this workspace and then build and run the product in Xcode, the updated framework is apparently not used. The product's behavior at runtime does not reflect the change.
What could be the problem? Possible issues:
1. My build settings still show an old location I used in Xcode 3 for built products, including the Framework Search Paths setting. My understanding is that Xcode 4 ignores these old Xcode 3 build settings and "does the right thing" automatically when the product uses the Xcode 4 DerivedData default location. Is this correct?
2. I have two workspaces that include the same framework project. One workspace contains only the framework project alone, because i use the framework in several products and want a convenient place to work on it. The other workspace is for this application, and it includes the application project and the same framework project. Both workspaces point to the same framework project folder, and changes I make to the framework project's source code is correctly reflected in the project no matter which workspace I look at.
However, after building the application workspace with new source code changes in the framework project, I see something surprising in the DerivedData folder. There are two folders named for the framework, one in the framework workspace folder and the other in a framework subfolder of the application workspace folder. Only the former is updated with a new framework executable after building the application workspace (judging by the modification date shown in Finder). So I deduce that, when I run the application in Xcode, Xcode may be finding the wrong built framework -- the old, unchanged framework executable in the framework subfolder of the application workspace folder in DerivedData, instead of the new framework executable in the framework workspace folder in DerivedData.
So it appears that the Framework Search Paths build setting does in fact honor the DerivedData default setting instead of the old Xcode 3 search path (issue #1, above) -- but it's picking the wrong executable out of the two executables in the DerivedData folder.
Is there a new Xcode 4 build setting I should use as the value of the Framework Search Paths build setting in my framework project? If not, should I type in a hard coded path to the correct framework folder in DerivedData? I just tried it with the hard-coded path, and it did not make any difference. And even if it did, how would I deal with the UUID that I assume might change from time to time in the DerivedData folder?
--
Bill Cheeseman - email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden