On Monday, August the 8th, Christopher Kempke wrote:
Again, assume a static lib S, in it's own xcode project. Application
A uses it, by including S's project, setting the dependencies, etc.
etc. (etc. etc. etc.....see previous whine) Everything builds fine.
Now, make a modification to a file in S, and hit "Build" in A's
project window. "A" knows that "S" is a dependency, and builds it,
but DOES NOT LINK AGAINST THE RESULTING LIBRARY. In other words, the
build step for A occurs, but has no content, because it doesn't think
anything has changed (it doesn't notice the new library, apparently).
This is 100% reproducible for me, and it's driving me nuts
This link problem is still happening here in Xcode 2.2. Did anyone ever
get to the bottom of this?
My link order is correct, and I don't have any headers in the 'Copy
Sources' build phase (these were the two suggested solutions when this
topic was raised previously).
Any help would be greatly appreciated.
James
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
