• 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: Getting Precompiled Headers To Share
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting Precompiled Headers To Share


  • Subject: Re: Getting Precompiled Headers To Share
  • From: Jean-Daniel Dupas <email@hidden>
  • Date: Thu, 30 Oct 2008 13:37:32 +0100

Le 30 oct. 08 à 12:19, Mark Coniglio a écrit :

Hi List,

My mom always taught me to "play nice" and share; I wish I could get XCode's precompiled headers to do the same. ;-)

I have 120 plugins sharing the same .pch file -- which actually just includes the Carbon framework. Yet, they are all producing individual precompiled header files, taking up gigabytes of disk space.

Here's two example hash files:


When I diff these files... these two lines are different:

-F/Volumes/MAMBOXP/sandbox/IsadoraPlugins/Desaturation/build/Release
-I/Volumes/MAMBOXP/sandbox/IsadoraPlugins/Desaturation/build/Release/ include


-F/Volumes/MAMBOXP/sandbox/IsadoraPlugins/Lookup/build/Release
-I/Volumes/MAMBOXP/sandbox/IsadoraPlugins/Lookup/build/Release/include


Now, the thing is -F is a Framework include option, and -I is an include directory option (as I understand it.) But I'm not specifying these two paths anywhere in the settings, as far as I can tell. These two include paths


-I../../Isadora/Isadora SDK/Headers
-I../../Isadora/Isadora SDK/Private

are specified explicitly by me, but they are the same for both.

I don't know why I'd end up with a -F option for the folder in which the built plugin resides (.../build/Release). And for the -I option, there is no "include" folder at ...build/Release/include -- again, the folder with the built plugin.

See the "Increase shargin of precompiled headers" build setting (GCC_INCREASE_PRECOMPILED_HEADER_SHARING).


And also "Precompiled Headers uses File From Build Directory" (PRECOMPS_INCLUDE_HEADERS_FROM_BUILT_PRODUCTS_DIR)

Use the doc button a the bottom to the build settings window to get advantage and drawbacks of these settings.

_______________________________________________
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: 
 >Getting Precompiled Headers To Share (From: Mark Coniglio <email@hidden>)

  • Prev by Date: Re: [Xcode-Users] Best Practice: Finding the Developer Folder
  • Next by Date: Re: Automatically Remove Unused #import Directives
  • Previous by thread: Getting Precompiled Headers To Share
  • Next by thread: [Xcode-Users] Best Practice: Finding the Developer Folder
  • Index(es):
    • Date
    • Thread