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: Quincey Morris <email@hidden>
- Date: Thu, 30 Jun 2011 14:18:41 -0700
On Jun 30, 2011, at 12:22, Bill Cheeseman wrote:
> I take it back -- I AM now seeing the expected behavior!!! So, problem solved.
Good to hear.
> But this still leaves me befuddled about the correct values to place in the Framework Search Paths build setting. The fact that it "just works" when I use the DerivedData default preference setting for build location, ignoring whatever garbage path I put in the Framework Search Paths build setting, is not exactly intuitive. At the very least, I suppose I should remove the old Xcode 3 path value that I no longer use.
I think you might be right about the "it just works" thing. I went through several iterations of configuring my build settings, because I didn't know what I was doing, because as you say nothing is documented in the places you might naturally look. I may have only needed the Frameworks Search Paths setting while something else was still wrong.
However, I still don't think Framework Search Paths is *ignored* because of the Xcode 3/4 build locations transition thing. I think it just isn't necessary for the "it just works" scenario, but still is necessary for an out-of-workspace framework reference.
> But what about all the related settings, like Build Products Path and similar settings in the Build Locations section. Are we just supposed to leave those blank when we use the DerivedData default location? Some clarity in the documentation would be a big help.
I think the documentation is clear enough, if you start from the Xcode System Guide or the Transition Guide. With Xcode 4's default workspace or preference location settings, these build location settings are ignored by Xcode 4 and honored by Xcode 3 with their old meanings (so Xcode use of the same project works as it always did). If you change the Xcode 4 location settings, you can choose to have it use the same build locations as Xcode 3 (that is, to honor the build settings), or to give it some more or less complicated custom arrangement. Basically, I think it's a three-way switch: new, old and do-whatever-you-want.
What's not clear is, if you start by looking at the building settings, determining which ones Xcode 4 ignores, which ones Xcode 4 interprets differently (if there are any), and which ones mean the same thing as Xcode 3. That's very frustrating.
_______________________________________________
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