Re: Xcode 4.3.3 problem with framework search paths SOLVED
Re: Xcode 4.3.3 problem with framework search paths SOLVED
- Subject: Re: Xcode 4.3.3 problem with framework search paths SOLVED
- From: lbland <email@hidden>
- Date: Fri, 15 Jun 2012 10:04:42 -0400
hi-
On Jun 15, 2012, at 9:39 AM, Bill Cheeseman wrote:
> I found a simple and intuitive solution, but it surprises me: I had to add my shared framework to my application target and make it an explicit dependency in the Target Dependencies build phase of my application target.
Our projects have the frameworks as explicit dependencies of the application target and that did not work.
I did notice that "adding a shared framework" to the project in Xcode 4.3.3 "magically" maybe seemed to correct the problem. So, it seems like there is something behind the scenes when adding a framework as opposed to just setting the framework up as a dependency of a target.
> In Xcode 4.3.2 this was not necessary; it was sufficient to include the framework in my application's workspace and rely on the Find Implicit Dependencies setting in the application target's Build scheme. This is no longer true in Xcode 4.3.3. In 4.3.3, until I set up an explicit dependency, the build fails when it gets to the first '#import <framework/framework.h>' in the application headers, saying it can't find the framework. The framework was not getting built first, so it didn't show up in the DerivedData folder where Xcode expected to find it..
>
> My shared framework is weak linked in the application project using -weak_framework in the Other Linker Flags build setting. That was true when I was using Xcode 4.3.2, too, so this has nothing to do with the issue. And it wouldn't, anyway, because the build fails way before it gets to linking.
>
> So, my only question now is: Is the failure of Xcode 4.3.3 to find the implicit dependency a bug?
IMHO: No. I think you should be required to mark dependencies explicitly, that is why files have a dependency [target] list. ??
> I can't image why Apple would want to kill that feature in the move from 4.3.2 to 4.3.3.
I don't know about this change, but I like it so far.
The things I would like in regards to this are:
(a) A third party SDK location. Where is that? It is not /Library/Frameworks (or should not be but that is a poor substitution until I know where the 3rd party SDK location should be).
(b) A -F path to the DerivedData locations of framework builds. (may be hard (not realistic) because they have an encoding in the path).
(c) Xcode plugins for 3rd parties for IB implementations. That is only remotely related to this current issue, But OTOH: Plugins are [should be] related to SDKs.
thanks!-
-lance
_______________________________________________
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