X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Mon, 20 Oct 2008 13:40:53 -0400 From: "Mark J. Reed" To: cygwin@cygwin.com Subject: Re: Compile time Local Cygwin vs. VMware session on same system In-Reply-To: <48FCBAC3.8090209@bmts.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48FCBAC3.8090209@bmts.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mon, Oct 20, 2008 at 1:07 PM, Ralph Hempel wrote: > It looks like you're comparing compiling under Cygwin on the > host machine to compiling under Linux on a VMWare machine running > on the host and finding the second way faster. Shocking! > Long story short, this is probably not so much a Cygwin issue > as general Windows issue... No, I think that's going too far. It's a mismatch between the Windows and UNIX process models, and the fact that compilation via make(1) is optimized for the latter. I suspect that compiling the same quantity of code on Windows would be plenty fast with a native Windows build system that made efficient use of threads and CreateProcess() rather than going through a simulation of fork(). - Mark J. Reed -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/