Re: Static lib linking (XCode 2.1)
Re: Static lib linking (XCode 2.1)
- Subject: Re: Static lib linking (XCode 2.1)
- From: "James Larcombe" <email@hidden>
- Date: Mon, 8 Aug 2005 12:06:09 +0100
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).
I have often had this problem. I haven't yet managed to get to the bottom
of it, but I did discover two supposed explanations.
1. Ensure the link order is correct. The documentation states (somewhat
obliquely?) that you have to have all the static libraries before any of
the dynamic libraries. This happened to be wrong in some of my projects
(my libraries were intermingled with frameworks). When I corrected it, I
thought at first that it had fixed the problem, but it later recurred.
2. In a post to this list on the 22nd of July, Chris Espinosa suggested
that having headers in the 'Compile Sources' build phases of the targets
would cause these sorts of problems. I think some of projects have ended
up in this situation - I'm going to sort them out and try it again, when
I get chance.
James
_______________________________________________
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