Re: Compiler pukes on Cocoa.h in .mm/.h file; __OBJ__ not defined
Re: Compiler pukes on Cocoa.h in .mm/.h file; __OBJ__ not defined
- Subject: Re: Compiler pukes on Cocoa.h in .mm/.h file; __OBJ__ not defined
- From: Kyle Sluder <email@hidden>
- Date: Fri, 27 Feb 2015 15:33:34 -0600
On Fri, Feb 27, 2015, at 03:20 PM, Jerry Krinock wrote:
>
> > On 2015 Feb 27, at 13:06, Kyle Sluder <email@hidden> wrote:
> >
> > What does the build log say for that file?
>
> Good question, Kyle. Hmmmm, the CompileC command says <blah blah> c++ in
> the place where it should say <blah blah> objective-c.
>
> If I recall correctly, there are some settings where you can map file
> types to what the compiler does with them. Probably someone has played
> with those. I thought those were in the “Build Rules” tab, but I can’t
> find them just now. Still looking.
Check the Compile Sources phase on the Build Phases tab. There is a
column for Compiler Flags; make sure that there isn't one there that
forces the file to be compiled as C++ instead of Objective-C++.
--Kyle Sluder
_______________________________________________
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