Static lib linking (XCode 2.1)
Static lib linking (XCode 2.1)
- Subject: Static lib linking (XCode 2.1)
- From: Christopher Kempke <email@hidden>
- Date: Sun, 7 Aug 2005 22:29:12 -0700
I posted a list of whines here a bit ago about static lib sub-
projects, one of which was that XCode wasn't noticing changes
consistently. I believe I can now be more specific.
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, because
I'm trying to debug changes in the static library, but unless I
remember to make a change in one of A's files, too, they're not
getting picked up. Is there something I can do to force it to see
the library? I'd be willing to let it link every time, whether it's
changed or not, if I can force that.
--Chris
_______________________________________________
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