• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Xcode Cannot Evaluate "Implicit Dependencies"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode Cannot Evaluate "Implicit Dependencies"


  • Subject: Xcode Cannot Evaluate "Implicit Dependencies"
  • From: Andreas Grosam <email@hidden>
  • Date: Thu, 26 Apr 2012 13:23:16 +0200

Xcode cannot always evaluate dependencies to libraries correctly.

If a source file of a library is edited, but the sources of the "main" product are un-touched, and the "main product" is build, the depended library is build correctly, but Xcode may not link the final executable, because it apparently compares modification dates to wrongly set file path pointing to the binary of the library. That is basically, "Debug"  and "Release" Configurations are mixed up, or the path to the binary does not exist at all.

This happens (or not) depending on how one has specified the reference to the library, and which Configuration/Destination is set. This is clearly a bug, which can also be seen in log files Xcode creates when checking the dependencies.


Has anybody found a workaround to this issue? I've tried several methods, but all fail at least in one condition. So, either Release or Debug builds or both do not build correctly, no matter how I set up the linked library.

In other words, "Find Implicit Dependencies" does not work.
It also means, finding more or less "direct" dependencies, does not work also.



Regards
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

  • Prev by Date: Re: Xcode seems to be generating bad code
  • Next by Date: Re: Xcode seems to be generating bad code
  • Previous by thread: Re: Xcode seems to be generating bad code
  • Next by thread: Tweak auto-completion
  • Index(es):
    • Date
    • Thread