Re: Build Issue With Static Lib
Re: Build Issue With Static Lib
- Subject: Re: Build Issue With Static Lib
- From: Andreas Grosam <email@hidden>
- Date: Sun, 11 Mar 2012 15:09:50 +0100
On Mar 11, 2012, at 2:49 PM, Andreas Grosam wrote:
> Hm, it seems the final product has not been updated. The object files of both the main product and those of the static lib and the binary of the static lib are actually younger than the executable.
>
> Doing a "Build" does not update the final executable. This is certainly a bug, no matter what. Relaunching Xcode does not help either.
>
> I suspect, this "stale executable" may happen when there is an active debug session and the product will be re-build. I would have been expected Xcode can manage this.
Found the culprit: a corrupt path for the static library in the "Link Binary With Libraries" List in the "Build Phases" pane of the build settings for the main product.
Those paths can break easily, for instance when changing the folder structure or, as in my case, attempting to link to a static lib whose binary does not yet exist (or has been cleaned). And this can happen quite too easy. Xcode has no robust way to accomplish this task, nor does it emit any hints or warnings.
Andreas
_______________________________________________
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