ARGH~ jeeze... Frigging hmaps (USE_HEADERMAP!)
It took way too long to figure this out. A whole... 2+ hours.
Here's the problem:
In XCode, due to their use of header maps (.hmap files), they confused system files with the header files my teacher gives me "string.h". This causes a problem, of course. I've also heard of this problem with time.h.
The solution when you have files with names that are the same as system ones?
-Project > Edit Project Settings (or, alternatively, select your topmost project thing in "Groups & Files" and hit command+i)
-Click on the "Build" tab, then the "+" button at the bottom of the first large field. Add "USE_HEADERMAP" as the setting, and then uncheck the value - a box will appear.
This will disable the use of headmaps for that build configuration ONLY, unless you have your "Configuration:" set to "All Configurations".
You may need to do this for the target too... (as in, add that as a setting.) I'm not too sure, nor do I really feel like checking that.
[EDIT] GAH! It broke again. Or something.
Here's the problem:
In XCode, due to their use of header maps (.hmap files), they confused system files with the header files my teacher gives me "string.h". This causes a problem, of course. I've also heard of this problem with time.h.
The solution when you have files with names that are the same as system ones?
-Project > Edit Project Settings (or, alternatively, select your topmost project thing in "Groups & Files" and hit command+i)
-Click on the "Build" tab, then the "+" button at the bottom of the first large field. Add "USE_HEADERMAP" as the setting, and then uncheck the value - a box will appear.
This will disable the use of headmaps for that build configuration ONLY, unless you have your "Configuration:" set to "All Configurations".
You may need to do this for the target too... (as in, add that as a setting.) I'm not too sure, nor do I really feel like checking that.
[EDIT] GAH! It broke again. Or something.