Re: CW to Xcode transition - Is more RAM worthwhile?
Re: CW to Xcode transition - Is more RAM worthwhile?
- Subject: Re: CW to Xcode transition - Is more RAM worthwhile?
- From: Jerry <email@hidden>
- Date: Wed, 21 Dec 2005 16:06:01 +0000
On 21 Dec 2005, at 15:47, Sean McBride wrote: On 2005-12-21 13:51, Jerry said:
CW, then you're wasting a lot of time per day. I suspect the main trouble is that CW has the compiler built in and only needs a single instance to compile every file in your project. XCode has to call gcc in batches and so it gets the whole startup and header file parsing overhead repeated many times during a build.
So Xcode creates a new gcc process for every file being compiled? Apparently, process creation is also rather slow on Mac OS X, say some:
Not quite, it seems to batch files up in groups and invokes gcc for each group. Presumably, the group size is affected by the maximum command line length or some such limit.
Jerry
|
_______________________________________________
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