Re: Problems with #include "" vs #include <>
Re: Problems with #include "" vs #include <>
- Subject: Re: Problems with #include "" vs #include <>
- From: Chris Espinosa <email@hidden>
- Date: Fri, 19 Dec 2003 16:19:15 -0800
On Dec 19, 2003, at 4:11 PM, Marshall Clow wrote:
This is almost certainly a headermaps issue. Turning off headermaps
in Xcode might do the trick.
I tried that, it almost worked.
In my main file, there was a #include "Foo.h", where Foo.h was in the
same directory
as the project. It couldn't find it :-(
I added an additional search path of '.', and it fixed that.
Now I'm getting other errors, but they're not missing include files
any more.
Thanks.
For those of you keeping score at home, Marshall added USE_HEADERMAPS =
NO to his target Build Settings to turn off header maps. That
eliminated the problem of header name ambiguity but also defeated the
default access to his project's headers.
I'd recommend using a specific Xcode build setting like $(SRCROOT)
instead of ".", as you cannot necessarily rely on the working directory
always being the source root of your project.
Chris
_______________________________________________
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.