Re: C++ gets translated into ObjC? Strange compiler errors...
Re: C++ gets translated into ObjC? Strange compiler errors...
- Subject: Re: C++ gets translated into ObjC? Strange compiler errors...
- From: "Brian Barth" <email@hidden>
- Date: Wed, 10 May 2006 22:18:20 +0200
Hi all
Thanks for your answers!
@ Michael J. Bergin
>Did you set the "Compile Source As" build setting for the target from
>"According to File Type" to "Objective-C++"? I also came across the
>following link that had some interesting compatibility information
>about objc++ and universal binaries near the bottom of the page.
>Hope that helps.
Yes, this is already set this way.
@ D. Pirnack
>If that will not solve your problem you might try to set a file based
>build setting,
>Set the other c flags to <-x objective-c++> which tells the
>precompiler that this file is an objective-c++
>file.
This flag is set for the compiler AND I also tried and set it for the
individual file in the like Scott proposed.
None of it worked though.
Still - what confuses me is that the exact same compiler settings, same
classes and same prefix-header content compiles without error the MainApp.
I also compared the compiler setting at the command line for both
targets just to make sure they are identical.
This still remains very weird - a kind of mystery as it seems like the
compiler translates c++ first into ObjC...
Shouldn't it be that the compiler (or some special preprocessor?)
translates ObjC to pure C?
Thanks for all your help, more ideas welcome.
Brian.
--
Experience is the name everyone gives to their mistakes.
-Oscar Wilde-
· · · b o b · · · (osXdriven) · · · www.bobthevisitor.de · · ·
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden