• 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: problems with UnitTests.octest
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems with UnitTests.octest


  • Subject: Re: problems with UnitTests.octest
  • From: Fritz Anderson <email@hidden>
  • Date: Mon, 31 May 2010 12:01:12 -0500

On 31 May 2010, at 2:20 AM, Pete Siemsen wrote:

> I had a running Mac OS X app.  I made a lot of disruptive changes to allow the code to run on other platforms.  The changes included renaming source files.  The new app runs, but the the unit tests don't.  When I try to build the unit test, I get this on the Console:
>
> Error   Cannot find executable for CFBundle 0x100109810 </Users/siemsen/play/objective-c/PetesLookup/build/Debug/UnitTests.octest> (not loaded)
>
> ...and I get 11437 (!) errors, none of which are in my code.  All the errors are similar - like
>
>
> In file included from /Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:8,
>                 from /Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/Cocoa.framework/Headers/Cocoa.h:12:
> /Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:180: error: expected identifier or '(' before '@' token
> /Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:182: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token

Given that these are the first points in NSObjCRuntime.h (or the files it #includes) at which Objective-C directives occur, it's safe to say they were choking a compiler that wasn't expecting Objective-C. The build transcript should have shown you what was being compiled that made the compiler emit errors. Is it possible that some of your "renamed" files were renamed from .m or .mm to .c or .cp? Do you have a prefix header that doesn't guard the Cocoa #imports with #ifdef __OBJC__?

> How can I approach this problem?  The program compiles and runs, and my unit test files compile.

	— F

 _______________________________________________
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: 
 >problems with UnitTests.octest (From: Pete Siemsen <email@hidden>)

  • Prev by Date: Re: Is dependency info supposed to persist?
  • Next by Date: Re: Is dependency info supposed to persist?
  • Previous by thread: problems with UnitTests.octest
  • Next by thread: Is dependency info supposed to persist?
  • Index(es):
    • Date
    • Thread