• 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: Baffling Xcode Complaint About Compiling My Object
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Baffling Xcode Complaint About Compiling My Object


  • Subject: Re: Baffling Xcode Complaint About Compiling My Object
  • From: Lance Drake <email@hidden>
  • Date: Wed, 3 Mar 2004 11:24:27 -0700

Hi Lance,
Is the MyMsgPort.h + .cpp the only C++ class defined in your project?

Hi ALun,

The funny part is that this WAS a plain ole vanilla "c" file header which was not working either - (because, I thought, it was not correctly making reference to an external Objective-C object) - so I changed the file to C++ formatting as an attempted remedy and found the results were still the same. Mebbe I should convert it to ObjC? In any event, that external reference has been eliminated as a gesture to getting it to compile on it's own - which has yet to happen.

Is the MyMsgPort.h file referenced anywhere else in your project, apart from
MyApp.h and MyMsgPort.cpp?

I put the "#ifndef __MyMsgPort_h__ protecting barrier in the header but it was no assist.
This is the first place it is referenced in the project - on the very first file-compile attempt.


Did you try changing the MyApp.m file to MyApp.mm? Might be worth a shot.

I did try that - no progress.

Alun

Thanks for your good time helping me think about how to solve this problem.


One interesting data point: A complaint was registered to the console to the effect:
2004-03-03 10:45:38.168 Xcode[1870] Unable to index /Users/lance/Apps/MyApp/MsgPorts/MyMsgPort.c: No such file or directory


Of course, the project has it listed as 'MyMsgPort.cpp' (and the file shows up in a Finder window as such) and the filetype is specified in the Info dialog as 'sourceCode.cpp' (which it is) and the header file (which seems to generate the initial complaint is showing as 'sourceCode.cpp.h' in the Info dialog.

I did a 'reindex' on the project - no assist, took a look at the project internals (as best I could) and did not find a 'MyMsgPort.c' file referenced anywhere. A good guy at Apple has suggested he might be able to take a look at the situation - I'll be sending a copy of the Project to see if they spot anything. Since the reindex, the error on the console is not appearing anymore, but the error persists.

My experience with Xcode has been really good. So far I have had few problems that weren't promptly dispatched. At least I'm not having to deal with the vagaries of the MS development world. I DO count my blessings!

Lance Drake
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


  • Prev by Date: Re: legacy library build can't find 'Preprocessor Macros'
  • Next by Date: Re: Using XCode to build webapps
  • Previous by thread: Re: Baffling Xcode Complaint About Compiling My Object
  • Next by thread: xcode plugin
  • Index(es):
    • Date
    • Thread