Serious Issue: References To Products Lost / Wrong Dependency Evaluation
Serious Issue: References To Products Lost / Wrong Dependency Evaluation
- Subject: Serious Issue: References To Products Lost / Wrong Dependency Evaluation
- From: Andreas Grosam <email@hidden>
- Date: Fri, 20 Apr 2012 11:07:14 +0200
After Cleaning the Build Folder, well at least it appeared this was the cause, many but not all file references to products within a Workspace obviously become broken. Xcode will color entries in the Navigator red, and even when a product has been build successfully and the file actually exist Xcode is unable to find the associated file.
How can I fix it?
Furthermore, it seems, this issue has an effect on dependency evaluation. Xcode will NOT build correctly anymore.
For instance when editing a source file which is a member of a library, and building the main product which links against this library, Xcode will build the library, but not linking the final binary anymore.
It is also quite obvious that Xcode creates malformed or false URIs to files (referencing libraries) which actually do not exist. This happens when using Build Phase "Link Binary with Libraries Panel", and is 100% reproducible. This is a long standing bug occurred and reported since the event of Xcode 4.0 and may cause a number of other issues. Is this really that hard to fix?
I suspect, those broken/wrong URIs to static libs and dylibs also seem to confuse Xcode when it checks dependencies. This then produces a wrong dependency chain, which as a result, causes the linker to not link correctly. There quite many sources reporting Xcode is failing in correctly evaluating the dependencies.
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