Re: Checking dependencies
Re: Checking dependencies
- Subject: Re: Checking dependencies
- From: Chris Espinosa <email@hidden>
- Date: Tue, 24 Feb 2009 16:06:59 -0800
On Feb 24, 2009, at 3:54 PM, Emile Tobenfeld (a. k. a Dr. T) wrote:
This seems to take 5 - 10 times as long in 3.1 than it did in
2.4/2.5, Anyone know why, or what can be done about it?
There's no general regression from 2.5 to 3.1 in Dependency Checking
times, but we do know of a handful of cases where Checking
Dependencies is pathologically bad. We don't have enough information
about these to determine why, but some suggestions are:
- certain network configurations hit a problem where searching for
"net/inet.h" causes a long NFS mount/timeout
- we've seen projects with 50-100 cross-project references that
exhaust system memory and cause Xcode to swap to death
- if your build folder is inside your project folder, and you have a
recursive user header search path pointing at your project folder, the
folder-walk time can grow exponentially
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. One piece of forensics that might help is to clean
your project, launch Terminal and type:
$sudo fs_usage Xcode > ~/XcodeFSUsage.txt
and open your project and click Build. When Checking Dependencies
ends, go back to Terminal and control-C, then attach the
XcodeFSUsage.txt file to the bug report.
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