• 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: Xcode 2.2 precomp link warning
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.2 precomp link warning


  • Subject: Re: Xcode 2.2 precomp link warning
  • From: Ricky Sharp <email@hidden>
  • Date: Sun, 13 Nov 2005 18:52:24 -0600


On Nov 13, 2005, at 12:50 PM, Chris Espinosa wrote:

On Nov 13, 2005, at 10:25 AM, Eric Albert wrote:

/usr/bin/ld: warning /Library/Caches/com.apple.Xcode.501/ SharedPrecompiledHeaders/AppKit-blqywaoivjvvmxbulbeesgzoomdp/ AppKit.h.gch.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded)

How bad does this warning rank on the badness scale? Is the linked product horribly broken as a result or is this just a minor thing?

In both cases here, the thing that stands out as odd is that the linker is being told to pull in your precompiled header. That doesn't make any sense. If you can figure out why that's happening, I bet you'll be able to track down the real problem. Perhaps the .pch file is in your compile sources build phase or something like that?

Is there any chance that your Compile Sources build phase might have the precompiled header (the .gch) listed in it? In that case Xcode will try to recompile the precompiled header to create an object file, then try to link that object file into the executable.

My .pch wasn't in the Compile Sources phase of either build config. However, it was being included in both targets (it was listed under the Other Sources folder and checked for inclusion to my targets).


Since my settings for both configs referenced the prefix file (Prefix Header), I removed the reference to the .pch. The development build still produced the warning. I then re-emptied the SharedPrecompiledHeaders folder inside of /Library/Caches, but the build still produced the warning.

Finally, I renamed my .pch and changed the value accordingly in the Prefix Header setting. Same outcome; development config produces the warning and the deployment one doesn't. Is this a case of a corrupt project?

___________________________________________________________
Ricky A. Sharp         mailto:email@hidden
Instant Interactive(tm)   http://www.instantinteractive.com

_______________________________________________
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


  • Follow-Ups:
    • Re: Xcode 2.2 precomp link warning
      • From: Ricky Sharp <email@hidden>
    • Re: Xcode 2.2 precomp link warning
      • From: Greg Hurrell <email@hidden>
References: 
 >Xcode 2.2 precomp link warning (From: Ricky Sharp <email@hidden>)
 >Re: Xcode 2.2 precomp link warning (From: Greg Hurrell <email@hidden>)
 >Re: Xcode 2.2 precomp link warning (From: Eric Albert <email@hidden>)
 >Re: Xcode 2.2 precomp link warning (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Test bundle can't find app
  • Next by Date: Re: Xcode 2.2 precomp link warning
  • Previous by thread: Re: Xcode 2.2 precomp link warning
  • Next by thread: Re: Xcode 2.2 precomp link warning
  • Index(es):
    • Date
    • Thread