Xcode finds a very remote header...how?
Xcode finds a very remote header...how?
- Subject: Xcode finds a very remote header...how?
- From: Andrew Duncan <email@hidden>
- Date: Thu, 13 May 2004 11:00:06 -0700
I'm doing a porting project, so I'm starting with a well-developed
folder hierarchy already, and trying to just compile one file at a
time, slowly untangling the dependency relations.
I'm expecting the compiler to report "Could not find include file
so-and-so" but to my surprise, even though the include file is five
folder levels higher, one over, and two back down from the .xcode
project file, Xcode finds it! I can verify the actual path of the file
by bringing it into the edit window (one of its lines triggers an error
so I can just click on the error msg) and command-clicking its window
title.
So... how did Xcode do the search to find this remote file? I have not
added anything to the preprocessor include directives. I have noticed
before that Xcode will find include files that share a directory with
compiled files, even if those include files are not in the "project
proper", i.e. I did not explicitly add them to the project. But this
behavior seems to verge on psychic.
Andrew
email@hidden
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.