Re: Dependency cycle for target "xxx.lib" detected: xxx.lib -> xxx.lib
Re: Dependency cycle for target "xxx.lib" detected: xxx.lib -> xxx.lib
- Subject: Re: Dependency cycle for target "xxx.lib" detected: xxx.lib -> xxx.lib
- From: Fritz Anderson <email@hidden>
- Date: Sun, 08 Dec 2013 16:58:24 -0600
On 6 Dec 2013, at 5:39 AM, Thomas Wetmore <email@hidden> wrote:
> I'm using Xcode 4 and have a few static libraries that provide infrastructure for my applications.
>
> When I build the libraries I get the warning: "Dependency cycle for target "xxx.lib" detected: xxx.lib -> xxx.lib"
>
> Intellectually I understand what the dependencies are, classes that mutually refer to one another. But my naive assumption is that the linker works it out if only because the ranlib program is run on the archive files. I've been getting this warning on just about every static library I've written for years, so certainly nothing urgent here. It is only a warning and I've never had any problems linking against these libraries.
>
> I've googled for information and I searched through the Apple and GNU docs for help understanding this warning message, but so far have had no success finding info that directly addresses this warning and its consequences. When I google the only real results I get are my posting of about this same question two and half years ago!
>
> Can anyone offer any context? Should I be worrying about these warnings?
I'd proceed from the notion that the error message means exactly what it says: Your target that produces xxx.lib depends on xxx.lib to build it. Check the Build Phases tab of your Target editor, and look at the Target Dependencies, Compile Sources, and Link Binary With Libraries phases to see if xxx.lib (or something that needs xxx.lib to build it) is present.
— F
_______________________________________________
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