Re: Serious Issue: References To Products Lost / Wrong Dependency Evaluation
Re: Serious Issue: References To Products Lost / Wrong Dependency Evaluation
- Subject: Re: Serious Issue: References To Products Lost / Wrong Dependency Evaluation
- From: Andreas Grosam <email@hidden>
- Date: Fri, 20 Apr 2012 12:44:25 +0200
On Apr 20, 2012, at 11:07 AM, Andreas Grosam wrote:
> 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?
After some trial and error, I was able to *partly* fix the issue :
In Xcode Preferences, I changed the Build Products Folder, which now is located inside the Workspace. Then I built a few projects. The product file references from several projects (iOS and Mac OS X) eventually changed from red to black - indicating that it has found the actual file.
After changing back to the former (the default) Build Products Folder (and deleting the local Build folder within the Workspace), the issue has eventually disappeared.
However, I found another issue:
In case of a static library for iOS, referencing a product's file apparently works only reliable for "Destination" "iOS Device" - for all other destinations when made active (which possibly have a different binary), Xcode obviously does not associate the corresponding file with the reference in the Navigator.
Once the "iOS Device" binary exists, the file reference remains black, no matter which is the active Destination and whether there exists actually a binary for this destination. Otherwise, if the binary for Destination "iOS Device" does not exist, the entry remains red, no matter if a binary exists or not for the active Destination.
It seems, Xcode only "monitors" a corresponding product file for Destination "iOS Device" and associates this with the file reference in the Navigator pane, but does not care about other possible binaries, which are dependent on another Destination and Configuration.
This is at least confusing, if not a bug.
What strikes me now is - since I chose to use a "custom" Build folder in Xcode's Preferences, I'm unable to perform "Clean Build Folder..". The menu is greyed out. I've no idea why this is the case. "Clean" works - but as expected it cleans only the intermediates and products of the *selected* Scheme's target. Yet another bug?
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