Xcode 4.3.3 problem with framework search paths
Xcode 4.3.3 problem with framework search paths
- Subject: Xcode 4.3.3 problem with framework search paths
- From: Bill Cheeseman <email@hidden>
- Date: Wed, 13 Jun 2012 08:50:06 -0400
My projects stopped building when I upgraded to Xcode 4.3.3. The reported error was that Xcode could not find my #imported <framework/framework.h>, even though Xcode 4.3.2 had no difficulty in this regard.
After fooling around a while, I discovered that I could make it start building again if I added an explicit "/Library/Frameworks" to the Framework Search Paths build setting.
But that is not ideal, because it assumes my framework is finished, installed and unchanging. I would prefer to get the framework headers from ~/Library/Developer/Xcode/DerivedData as before, since I include the frameworks in my workspace so I can build them automatically if I make changes in them during development of the dependent application project. That used to work in 4.3.2, but no longer in 4.3.3. Why not? My Xcode preferences still specify the default derived data location, and I thought that was supposed to override any settings in Framework Search Paths for these purposes.
Or, a more general question, what is the proper setup when a shared framework is in the same workspace with an application project that is dependent on the framework?
--
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