• 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: Mon, 7 Feb 2011 15:31:34 -0600
  • Acceptlanguage: en-US
  • Thread-topic: Very long "Check Dependencies" phase

Hi Chris,

Thanks for the reply. That's a good point (and that might be why my bug report has been ignored)… I assume we can't get into Xcode 4 specifics on this list, but even if they've changed the way that works, we won't be able to move up in the near future for a couple of unfortunate reasons.

I'm hoping there might be some architectural changes we can make to soften the blow in the mean time. From Chris Espinosa's post on 2/24/09: "The more information you can provide (in private, in a http://bugreporter.apple.com report) the more we can help you out, often with project reconfiguration."

I was thinking that would be kind of neat. :)

Thanks,
Jeff

From: Chris Suter <email@hidden>
Date: Mon, 7 Feb 2011 14:50:29 -0600
To: Jeff Nordquist <email@hidden>
Cc: "email@hidden" <email@hidden>
Subject: Re: Very long "Check Dependencies" phase

Hi Jeff,

On Tue, Feb 8, 2011 at 6:31 AM, Nordquist, Jeff
<email@hidden> wrote:

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,

You should try Xcode 4. I imagine Apple aren't that bothered with
version 3 any more.

Kind regards,

Chris

 _______________________________________________
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: 
 >Re: Very long "Check Dependencies" phase (From: Chris Suter <email@hidden>)

  • Prev by Date: Re: Copying old instead of new Bundle Resources
  • Next by Date: Re: Silently failure to link Good-looking dylib
  • Previous by thread: Re: Very long "Check Dependencies" phase
  • Next by thread: Re: Very long "Check Dependencies" phase
  • Index(es):
    • Date
    • Thread