<div dir="ltr"><div class="" style="float:left;font-family:palatino,georgia,verdana,arial,sans-serif;line-height:19.200000762939453px;text-align:justify"> <br><a target="_top" href="http://gravatar.com/" rel="nofollow" style="color:rgb(0,51,102);font-weight:bold;text-decoration:none;font-size:x-small"><img border="0" alt="Gravatar" src="http://cache.gmane.org//gmane/comp/programming/tools/cmake/user/46424-gravatar"></a> <br>
</div><span style="font-family:palatino,georgia,verdana,arial,sans-serif;line-height:19.200000762939453px;text-align:justify"></span><h3 class="" style="margin:0px 0px 20px;padding:0px;font-family:palatino,georgia,'times new roman',serif;font-size:medium;color:rgb(0,51,102);line-height:19.200000762939453px;text-align:justify">
Re: cmake script profiler</h3><pre style="line-height:19.200000762939453px;text-align:justify">On 4/24/2013 5:37 AM, Gregoire Aujay wrote:
> Hello,
>
> Are you using cmake with a Makefiles generator on Windows ?
>
> From my experiments here are my observations:
>
> -Makefiles on Windows: slow
>
> -Visual ide generator : fast
>
> -Makefiles on linux: fast
>
> I found that when there are many targets in a project, cmake has to
> write many small files on the HD which seems to be very slow on windows.
>
> Regards,
>
> Gregoire
>
So, I just did some timing on ParaView which is a big project (includes
VTK). This is all on windows. It seems that ninja is the slow one.
The makefile and VS 10 generator were about the same. This is a second
configure, so it does not include the initial try-compile stuff which
can be slow on windows.
vs 10 real 2m41.935s
ninja real 3m33.807s
unix makefiles real 2m43.696s
-Bill</pre></div>