Re: Xcode 4 DerivedData folder and Framework Search Paths
Re: Xcode 4 DerivedData folder and Framework Search Paths
- Subject: Re: Xcode 4 DerivedData folder and Framework Search Paths
- From: Bill Cheeseman <email@hidden>
- Date: Thu, 30 Jun 2011 15:07:06 -0400
On Jun 30, 2011, at 1:26 PM, Quincey Morris wrote:
>> 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?
>
> The Framework Search Paths setting is not ignored by Xcode 4.
>
> In a project with a similar setup to yours, I have this set to the folder containing the framework project. Note that this isn't the location of the built framework (either intermediate or final), but Xcode figures out the correct location via some magic private recipe. Although the presence of the framework project inside the workspace is the secret sauce that makes this work, it's not the whole reason -- without the Framework Search Path build setting I still get compiler and linker errors.
It turns out that the immediate problem I was confronting was completely unrelated. I had moved my framework project to another folder before doing all this, and I mistakenly assumed that re-adding the framework project to my application workspace would automatically reestablish the application project's dependency on the framework. I was wrong. When I went to edit the Build Scheme for the application workspace, I found that the Build Scheme still thought the framework was "missing." I added the framework at its new location to the Scheme, and now the workspace is correctly building the framework and updating its executable in the framework subfolder of the application workspace.
And it is doing this WITHOUT my having put the framework project folder's path into the Framework Search Paths build setting, as you recommended I do. So I question your conclusion that this is necessary. Now that I've corrected my Build Scheme, it appears that Xcode 4 is in fact ignoring the old Xcode 3 Framework Search Paths value and automatically updating the application project's framework executable in the DerivedData folder.
But I'm still not seeing the expected behavior of my framework, so something is still wrong.
--
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