site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) As to where these are set? The various target build prefs. -- Andrew White -------------------------------------------------------------------------- This email and any attachments may be confidential. They may contain legally privileged information or copyright material. You should not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages. We do not accept liability in connection with computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment. This notice should not be removed. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Roland Silver wrote: What algorithm does xcode use to find files specified by #import <foo.h> and #import "bar.h" ? If someone can tell me where in the documentation to find the answers to these questions, rather than answering them directly, so much the better. At the basic level, I'm pretty sure they're semantically identical to the #include search paths, which are documented in the gcc documentation. As to what paths XCode adds so that they get searched as intended, if you click the "lines of text" button in the divider bar in the XCode results window you'll get another text field listing the actual gcc commands. From there you can read off the exact search path flags (typically -I and -L). This email sent to site_archiver@lists.apple.com