Re: Indirect framework reference problems
Re: Indirect framework reference problems
- Subject: Re: Indirect framework reference problems
- From: Eric Albert <email@hidden>
- Date: Mon, 2 Feb 2004 02:13:01 -0800
At 7:08 PM -0500 2/1/04, Mike Laster wrote:
Now imagine at some later point FrameworkA gets some new
functionality, and in the process, it gains a dependency on
NewFramework.framework. I modify the project for FrameworkA to add
a framework reference to
'/Marketocracy/Frameworks/NewFramework.framework', and FrameworkA
builds just fine without NewFramework.framework being installed,
since Xcode
again does it's magic and knows to look in the build products
directory for NewFramework.framework.
However, CommandLineTool no longer will link, even though it doesn't
actually reference any symbols in NewFramework.framework (it hasn't
changed at all from the point where it did work). As far as I can
tell, Xcode requires me to add a framework reference to
NewFramework.framework in my CommandLineTool project in order for it
to link. For some reason, its magic fails it and it doesn't realize
to look in my build products directory unless there is an explicit
framework reference.
In the 3 project case this isn't too bad, but with 100 projects,
it's a real pain to go through them all and add a new framework
reference just to be able to build.
Is there an easier way??
I'm not an expert on the linker by any means, but I think linking
FrameworkA with '-sub_framework NewFramework' might allow you to have
CommandLineTool link only against FrameworkA. On the other hand,
maybe it won't....
-Eric
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.