• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: compiling issues with .m and .cpp combination
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: compiling issues with .m and .cpp combination


  • Subject: Re: compiling issues with .m and .cpp combination
  • From: Jeremy Pereira <email@hidden>
  • Date: Tue, 20 Jan 2009 14:17:29 +0000


On 20 Jan 2009, at 13:59, Arnab Ganguly wrote:

Hi All,
Below I have given the build transcript.I am not able to resolve the error caused by "Wasabi/bfc/platform/platform.h:480:17: error: new.h: No such file or directory"
new.h files are present under the dir /Developer/iphone-installs/ SDKs/MacOSX10.5.sdk/usr/include/c++/4.0.0/backward and
...

When I compile all cpp files there seems to be no issue, but when there is a combination of cpp and .m files I am getting the above issue.
Do I need to change any settings in the project for the inclusion of the above file or any other settings I need to do?
Thanks in advance
-A



The .m suffix indicates Objective-C not Objective-C++. I would imagine that when compiling Objective-C, the compiler does not put C++ specific include directories in the include path, so it can't even see that file.


In fact, having taken a peek at it, there's no way Objective-C will compile it without errors since it consists entirely of namespace declarations.
_______________________________________________
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
References: 
 >compiling issues with .m and .cpp combination (From: "Arnab Ganguly" <email@hidden>)

  • Prev by Date: compiling issues with .m and .cpp combination
  • Next by Date: RE: compiling issues with .m and .cpp combination
  • Previous by thread: compiling issues with .m and .cpp combination
  • Next by thread: RE: compiling issues with .m and .cpp combination
  • Index(es):
    • Date
    • Thread