Fwd: Include directory confusion in XCode
Fwd: Include directory confusion in XCode
- Subject: Fwd: Include directory confusion in XCode
- From: Giovannini <email@hidden>
- Date: Fri, 18 Mar 2005 18:09:19 -0600
Thank you for the replies.
Here is the answer...
Begin forwarded message:
From: Richard Knight <email@hidden>
Date: March 18, 2005 11:54:37 AM CST
To: Giovannini <email@hidden>
Cc: email@hidden
Subject: Re: Include directory confusion in XCode
Hi,
The solution (I think!) is to add USE_HEADERMAP as a custom setting in the target's Build settings list, and set it to NO. That's what made it go away for me anyway.
Another one I hit when I first started using XCode is if you're writing C++ and start getting lots of 'template with C linkage' errors for no apparent reason, set the 'C Dialects to Precompile' Build setting to c++ rather than leaving it blank.
Yet another bug I get that I haven't found a way around yet is when compiling a project is getting a load of errors like:
Carbon.h:29: HIToolbox/HIToolbox.h: No such file or directory
Carbon.h:33: CarbonSound/CarbonSound.h: No such file or directory
Carbon.h:37: OpenScripting/OpenScripting.h: No such file or directory
Carbon.h:41: Print/Print.h: No such file or directory
Carbon.h:45: NavigationServices/NavigationServices.h: No such file or directory
Carbon.h:49: CommonPanels/CommonPanels.h: No such file or directory
Carbon.h:53: HTMLRendering/HTMLRendering.h: No such file or directory
Carbon.h:57: SpeechRecognition/SpeechRecognition.h: No such file or directory
Carbon.h:61: SecurityHI/SecurityHI.h: No such file or directory
Carbon.h:65: Ink/Ink.h: No such file or directory
Carbon.h:69: Help/Help.h: No such file or directory
Carbon.h:73: ImageCapture/ImageCapture.h: No such file or directory
when I compile anything. Hit build a second or third time and it compiles fine.
So hope XCode 2.0 sorts a lot of these things out - I'm amazed they managed to release 1.5 with them in. Just hope they haven't spent all their time putting the big new features in rather than fixing all the little bugs like this...
Cheers,
Rich.
On 18 Mar 2005, at 14:48, Giovannini wrote:
Hello,
I have spent countless hours on this one. The most frustrating part is that the setup sometimes (rarely) works. Here is the glitch.
Third party library (C++ source and headers) has a file called "Signal.h". XCode confuses the project relative Signal.h with the system's signal.h. Other system headers end up including the local.
The project is organized as such...
The XCode project file is in the root of the third party project directories
All source and header files are in a "source" subdirectory
/Users/dave/Projects/Project_Root/source/*.h,cpp,inl
All source files use #include "source/file.h,inl"
In order for XCode to see any of the project headers, I added the complete path of the "Project_Root" directory to the target's Include Header Path attribute. The man-pages then state that adding a " -" after the path specification will only use that path for #include "". It appears to be ignoring the flag.
To figure out what setting is causing the problem (there is a GMake file that works), I copied XCode's compilation command to the command line. The following parameter, when removed, compiles the file on the command without error.
-Wp,-header-mapfile,/Users/dave/Projects/Project_Root/source/build/project.build/project.build/project.hmap
What is going on? How do I tell XCode that "source/Signal.h" is not <singnal.h>?
_______________________________________________
MacOSX-dev mailing list
email@hidden
http://www.omnigroup.com/mailman/listinfo/macosx-dev
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden