Problems with #include "" vs #include <>
Problems with #include "" vs #include <>
- Subject: Problems with #include "" vs #include <>
- From: Marshall Clow <email@hidden>
- Date: Fri, 19 Dec 2003 14:06:49 -0800
Ok --
I'm spending the day trying to learn Nitrogen, a set of C++ wrappers
for Carbon.
(it's on SourceForge, for those of you who are interested)
It has a set of headers, with names that are the same as a bunch of
the Carbon headers.
So, in my code I have:
#include "Nitrogen/CFDate.h"
[ I have a source tree pointed at the Nitrogen folder, and
$(Nitrogen) added as a search path) ]
Inside Nitrogen/CFDate.h, this is what I see:
#include <CFDate.h> // Include Carbon's CFDate
namespace Nitrogen {
// lots of stuff here
}
The problem is that the line #include <CFDate.h> just includes the
same file again,
rather than getting the system's one. :-(
I tried adding another search path for
"/Developer/Headers/FlatCarbon" in my project,
before the search path for Nitrogen. No difference. I tried hacking
up the command line
passed to gcc (via Other_C_Flags) to contain "-I-
-I/Developer/Headers/FlatCarbon".
No difference. I updated from XCode 1.0.1 to Xcode 1.1. No difference.
How can I convince XCode/gcc to search for files delimited by "" and
<> differently?
[ Obligatory comment: Dang, this stuff is easy in CodeWarrior. ]
--
-- Marshall
Marshall Clow Idio Software <mailto:email@hidden>
Hey! Who messed with my anti-paranoia shot?
_______________________________________________
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.