Re: Mysterious error... to a newbie
Re: Mysterious error... to a newbie
- Subject: Re: Mysterious error... to a newbie
- From: Chris Espinosa <email@hidden>
- Date: Mon, 5 Dec 2005 15:16:25 -0800
On Dec 5, 2005, at 3:03 PM, Bob Stuller wrote:
Art, Ahoy, ahoy!
On 12/5/05, Art Isbell <email@hidden> wrote:On Dec 5, 2005, at 11:44 AM, Bob Stuller wrote:Now, interestingly (maybe!), the Console pops up with a slew of errors of this type:
2005-12-05 15:57:51.418 Xcode[4689] Unable to index /Applications/Metrowerks CodeWarrior 10.0/MetrowerksCodeWarrior/MacOSSupport/PowerPlant/UtilityClasses/UScreenPort.h: No such file or directory
just about the time that the linking should be taking place. The disquieting part about the path above: I knocked the spaces out of "Metrowerks CodeWarrior 10.0" days ago & cannot find any path that shows the spaces anywhere in Xcode.
So my first question is: What entity is sending error messages to Console about indexing
Xcode
I am betting that the alternate answer is 'ld' the command-line thingy that links the object code into an executable.
That's almost certainly incorrect. Indexing and linking are entirely separate. The warning is happening because the index is trying to update the contents of a file that is listed in your project but is not present on disk (because you "moved" it on disk by changing its pathname). Reindexing might eliminate this warning; you may also need to change the "Source Tree" (Xcode -> Preferences -> Source Trees -> Metrowerks CodeWarrior) to your PowerPlant headers in order to find the new location of the header.
& where does it get its path information?
From its index.
That is incorrect. The index is used only for UI navigation (code completion, Jump to Definition, etc.). The index is not used for building at all. The index gets all its path information from the project and from user preferences, not the other way around.
And the important question: Is this the source of the failure to link?
Likely.
Very unlikely. Link failures come from failure to find libraries and compiled objects. The warning above is the failure to find a header file. The linker never sees header files.
Tell Xcode to reindex the project (double-click or Get Info on the top group in Groups & Files and click "Rebuild Code Sense Index"). Then build again.
Hmmm... Sounded logical but didn't work. Thanks for taking a stab at this problem. Now what?
You'd have to post the actual linker error for us to help you resolve it. It may be related, that is, your project may also be linking against some library that was also in the path you changed. Select the blue Project icon and look in the Detail list for anything that's labeled in red type. Those are missing references. Select them and choose Get Info and you can fix up the references to make sure Xcode can find those files at build time.
Chris
_______________________________________________
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