• 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 [Solved]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2.2 precomp link warning [Solved]


  • Subject: Re: Xcode 2.2 precomp link warning [Solved]
  • From: Greg Hurrell <email@hidden>
  • Date: Tue, 15 Nov 2005 18:07:14 +0100

El 14/11/2005, a las 16:53, Ricky Sharp escribió:

On Nov 14, 2005, at 7:48 AM, Ricky Sharp wrote:

On Nov 13, 2005, at 6:52 PM, Ricky Sharp wrote:

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?

I opened up my project's project.pbxproj in TextEdit and looked for "Prefix.pch". It found three lines like this...


	GCC_PREFIX_HEADER = Source/IIDrills_Prefix.pch;

...in the buildSettings section of the Development, Deployment and Default configurations.

However, there was a fourth one in a PBXNativeTarget section:

	GCC_PREFIX_HEADER = Source/Drills_Prefix.pch;

Note that the name of the .pch. This was the original name I had. When renaming to "IIDrills_Prefix.pch", apparently this section went untouched.


I think I'm going to create a new app project from scratch and slowly add my project files to it. Perhaps this warning is some holdover from having converted non-native targets way back when?

Rather than create a whole new project, I just added a new target (Cocoa application type). I then added the appropriate files and changed settings for all configs as needed (deploy, debug, default).


Now, clean builds of the debug config (along with the other configs) does not generate the link warning.

I also solved the problem, but by other means. I tried toggling build settings on and off and I found one that got rid of the warning. The culprit was:


GCC_ENABLE_SYMBOL_SEPARATION

When turned off, the warning goes away. When turned back on, the warning comes back (only for when linking for i386). I don't remember ever explicitly setting this build setting myself. It appears to be on by default, as its description in Xcode says:

When precompiling a prefix header, generate a separate file containing the debug symbols for the PCH. This can improve build time, and is on by default for products other than static libraries. This option cannot be used when ZeroLink is enabled, and can only be used when the Level of Debug Symbols setting is 'All Symbols' (full).

As I said before, I don't know why this is happening with those projects (about 2 out of 20 projects). One is a normal Cocoa application and the other a Preference Pane. None of the other projects (Cocoa apps, Frameworks, Preference Panes, Bundles) produce warnings.


Cheers,
Greg


_______________________________________________ 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: 
 >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>)
 >Re: Xcode 2.2 precomp link warning (From: Ricky Sharp <email@hidden>)
 >Re: Xcode 2.2 precomp link warning (From: Ricky Sharp <email@hidden>)
 >Re: Xcode 2.2 precomp link warning [Solved] (From: Ricky Sharp <email@hidden>)

  • Prev by Date: Re: Subversion SSH authentication
  • Next by Date: Breakpoints that never go away
  • Previous by thread: Re: Xcode 2.2 precomp link warning [Solved]
  • Next by thread: Re: Xcode 2.2 precomp link warning
  • Index(es):
    • Date
    • Thread