On Mar 22, 2005, at 7:59 PM, Luc Vandal wrote: Header Search Paths /Developer/SDKs/MacOSX10.1.5.sdk/System/Library/Frameworks/Cocoa.framework/versions/a/headers
Header Search Paths should point to directories outside your project that have headers you include using either #include <file> #include <directory/directory/file>
You don't need to provide an entry for frameworks or for headers in your project, or for system headers in /usr/include.
For your purposes, this build setting can be blank. Framework Search Paths /Developer/SDKs/MacOSX10.1.5.sdk/System/Library/Frameworks/Cocoa.framework/versions/a/headers
The Framework Search Path should point to the directory that your framework is in. It's used for includes like
#include <fwk/fwk.h>
Since you're trying to use an SDK with a compiler that doesn't really support it, you need to set this to the directory that contains the framework you're trying to include. That would be
/Developer/SDKs/MacOSX10.1.5.sdk/System/Library/Frameworks
(Note that you don't need to go all the way into the Headers folder, and that your paths should always be case-correct) Installation Build Product Location (I assume that's the command-line option thingny) -F/Developer/SDKs/MacOSX10.1.5.sdk/System/Library/Frameworks/Cocoa.framework
-F is the same thing as Framework Search Path, and has nothing to do with Installation Build Product Location.
The Installation Build Product Location is only used when you use 'xcodebuild install' on the command line. You can probably leave this setting blank. Other Warning Flags -nostdinc
You need that to avoid the multiple includes you were getting; this may be OK.
Chris |