On 11/28/05, Paul Walmsley <email@hidden> wrote:
> > This is the same bug we mentioned in a thread last week (followed by
> thunderous silence :-)
> http://www.cocoabuilder.com/archive/message/xcode/2005/11/25/1472
>
> The situation as I've found it as where you have a command line
> executable (eg via the C++ tool template) that statically links against
> a couple of libraries that are listed as sub-project dependencies.
> Modifying any file in one of the sub-projects causes that library to be
> rebuilt but the linking phase is omitted. You have to manually delete
> the executable in order to force a relink. It doesn't seem to make any
> difference whether it's debug or release. Zerolink is off.
>
> So we have 3 xcode project files - A.xcodeproj, B.xcodeproj and
> C.xcodeproj. The first two each contain a single target - static libs
> A and B. The last one contains a single executable target C. The C
> project has dependencies on A.xcodeproj and B.xcodeproj and the C target
> links against the A.a and B.a libraries. There's also a cpp file that
> defines main() and calls functions in libs A and B.
Ahhh great. well not great because you suffer from the same problem,
but at least I don't feel isolated.
Don't hesitate to fill a bug if you didn't do so already.
Any comments from apple guys ? ;)
Thanks,
--
Olivier Tristan
_______________________________________________
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
This email sent to email@hidden
