> Mark Kirkwood <markir@paradise.net.nz> writes:
> > I was doing exactly this about a year ago and used Mingw. The only
> > annoyance was that I could compile everything on Linux in about 3
> > minutes (P4 2.8Ghz), but had to wait about 60-90 minutes
> for the same
> > thing on Windows 2003 Server! (also a P4 2.8Ghz...). So I used to
> > build a 'go for coffee' task into the build and test cycle.
>
> Youch! That seems unbelievably bad, even for Microsloth.
> Did you ever identify what was the bottleneck?
The mingw gcc compiler is horribly slow. It has nothing to do with
Microsoft this time. I haven't seen times quite that bad, but it's much
slower than gcc on Linux.
(As a comparison, completely rebuilding pgAdmin3 with Visual C++ on my
slow laptop takes maybe 5-6 minutes, whereas it takes 20+ minutes on a
Athlon64 3200+, with a much faster SATA disk and twice the memory. And
it's almost as slow on a dual-CPU server with high-speed SCSI disks. So
Visual C++ certainly doesn't have this problem.)
//Magnus