• 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: Very long "Check Dependencies" phase
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Very long "Check Dependencies" phase


  • Subject: Re: Very long "Check Dependencies" phase
  • From: "Nordquist, Jeff" <email@hidden>
  • Date: Thu, 10 Feb 2011 13:44:01 -0600
  • Acceptlanguage: en-US
  • Thread-topic: Very long "Check Dependencies" phase

Greetings (again),

I just wanted to mention for the record that I've had some success deleting the .dep files located in the Build directory. The time spend checking dependencies drops quite a bit after deleting them, and stays down for several builds (possibly until the next project change, though I haven't been able to verify that yet). Perhaps Xcode can create a new dependency map faster than it can verify an old one?

Anyway, if anyone else experiences this, that may be an option to explore…

Thanks,
Jeff


From: Jeff Nordquist <email@hidden>
Date: Mon, 7 Feb 2011 13:31:22 -0600
To: "email@hidden" <email@hidden>
Subject: Very long "Check Dependencies" phase

Greetings,

Recently the "Check Dependencies" build phase has started taking a long time (anywhere from 2 to 10 minutes). Our project is fairly massive; roughly 1100 source files and several large libraries (Boost, etc.). We're using Xcode 3.2.5. From the Google, it seems that others have experienced this as well, starting in Xcode 3.x.

I've tried the solutions I've found on this list and other places, including:
1. Adding some directories to PATH_PREFIXES_EXCLUDED_FROM_HEADER_DEPENDENCIES.
2. Looking for poor header include habits (headers including unnecessary headers, etc.)
- Is there a way to generate a full report of headers that are included during a build?
3. Checking to make sure we're not recursively including our build directory

At one point, Chris Espinosa suggested getting a report of Xcode file usage using "sudo fs_usage Xcode > ~/XcodeFSUsage.txt". When I tried that, the report file grew to about 9.5 Gigs before I started getting errors in Terminal. I filed a bug a month and a half ago (radar #8783217) but it seems to be untouched.

Here are my questions:
1. Is there something else I can try?
2. What dependencies is Xcode "checking"? Headers? Libraries? Is it building a map of some sort? Where is this map stored?
3. Are there some utilities other than fs_usage that might help me dissect the problem?

Thanks for any advice,
Jeff Nordquist

 _______________________________________________
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: 
 >Very long "Check Dependencies" phase (From: "Nordquist, Jeff" <email@hidden>)

  • Prev by Date: Re: Adding a target dependency
  • Next by Date: [ANN] Cong 0.7
  • Previous by thread: Re: Very long "Check Dependencies" phase
  • Next by thread: OK to share managed object model across MOCs?
  • Index(es):
    • Date
    • Thread