| Greetings -
I found a post from Sat, 29 Aug 2015 17:06:21 -0700 using a web search for the error message noted therein, and have found a solution that works for me. I’ve joined the list to post this, in case Carl is still having an issue with this...
Xcode 6.4, OS X 10.10.5
Xcode suddenly refuses to build a certain Cocoa project. (Other Cocoa and iOS projects build okay.) I brought out a backup copy of the project, and it refuses to build that, too.
I'm getting many of the following bizarre errors:
/opt/local/include/unctrl.h:60:63: error: unknown type name 'SCREEN'
NCURSES_EXPORT(NCURSES_CONST char *) NCURSES_SP_NAME(unctrl) (SCREEN*, chtype);
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:11:10: fatal error:
could not build module 'Darwin'
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6:10: fatal error:
could not build module 'CoreFoundation'
/Users/carl/Desktop/Projects/XOAS_29Aug2015/XOAS/XOAS-Prefix.pch:8:13: fatal error: could not build module 'Foundation'
#import <Foundation/Foundation.h>
^
Something is fundamentally wrong. I've reinstalled Xcode and the commandline tools. How can I proceed?
-Carl
My error was initiated from "#include <stdio.h>” in my project. Since the error happened virtually at the top line of my first .c file, I decided to make a throwaway “hello world” C program using the Command Line Tool template in Xcode 7, and see just how fundamental the problem was. Of course it worked…so I added /opt/local/include to my header paths, and it still worked. So, I created an entirely new Xcode project, using my actual source files, added /opt/local/include to the header path, added my /opt/local/lib libraries for linking, and it all works again…
A comparison of the working and non-working projects did reveal some differences, but nothing that would seem to be able to cause the problem, and my attempts to change Build Settings in the non-working project to match what was in the working project did not succeed…
My suggestion: Carl, if you’ve not done so, try re-creating your project in the latest Xcode for your version of OS X; also you might want to update your MacPorts packages.
Hope this helps…
— Philip
|