I have the same problem.Did you get it ?  

I have the same problem.Did you get it ?  

Just FYI: I had this problem mysteriously re-appear when I tried to do my distrubution build yesterday.

Had to do all the -fno and path settings over again in the other target.

Targets are very annoying :-(

Excellent!

I suspect that basically had the same effect as the pop-up I was mentioning.

I forgot to mention. It got solved after i deleted manually .mm file and put it back and build again freshly.

No, I definitely didn't have any problems until I did a #import of one of their headers into one of my VC's.

Suggest this: click on each of the files you brought into the project and look in the info screen on the right side (assuming Xcode here). One of the sub-screens has a pop-up that defines the file type. Make sure they're all set to Obcj-C++. You'll see it.

thanks for the reply! This is where I tried to find out to change to .mm, but the thing is, i have never called yet any of this vuforia aug. reality functions inside my application files yet. I just integrated aug. files and trying to make the build working as of now, without success. Or else you are saying all of my other files also to be changed to .mm, even though its not calling any of this vuforia aug. reality functions? Is there any other way which is causing this issue? 

The problem occurs at the "topmost import". In other words, if you import ANYTHING from the sample code into a pre-existing code base, that's where the problem lies. You need to change that file to be a .mm.

For instance, in my code base I had a file called "mapVC.m" that controlled a (get this!) a MKMapView. I wanted to use a pushViewController to insert their EAGLView when the user clicked on a button. As soon as I imported the .h, this error started occuring.

I went nuts trying to find it, because the compiler was always complaining inside another file. It wasn't saying that mapVC had a problem, it said that EAGLView did.

So change the "topmost class" to .mm and I'll bet it works.