[Interest] porting to Qt 5.4 - MOC very slow on Windows

[CaryT]

Keith Gardner <kreios4004 <at> gmail.com> writes:

> 
> 
> On Thu Jan 15 2015 at 12:33:59 AM Hamish Moffatt <hamish <at> 
risingsoftware.com> wrote:I'm trying to port our app from Qt 4.8 to 5.4. 
Currently working in MSVC
> 2013, and using the pre-built Qt binaries for that environment.
> We have about 440 files being MOCed during build. On 5.4, each file is
> taking 2-3 seconds meaning the overall build is significantly longer
> than in 4.8.
> I found a reference to a similar problem here -http://qt-
project.org/forums/viewthread/47901 - which was due to using
> MOC on a network drive. In my case everything is on local SSD.
> Any suggestions?
> 
> Do you have the /MP flag set for your project?  Even though MOC takes 
longer, this will at least allow you to run one instance of MOC for every core 
on your system in addition to reducing build times in general.
> 
> 
> 
> <div>
> <br><br><div class="gmail_quote">On Thu Jan 15 2015 at 12:33:59 AM Hamish 
Moffatt <<a href="mailto:hamish <at> risingsoftware.com">hamish <at> 
risingsoftware.com</a>> wrote:<br><blockquote class="gmail_quote">I'm trying 
to port our app from Qt 4.8 to 5.4. Currently working in MSVC<br>
> 2013, and using the pre-built Qt binaries for that environment.<br><br>
> We have about 440 files being MOCed during build. On 5.4, each file is<br>
> taking 2-3 seconds meaning the overall build is significantly longer<br>
> than in 4.8.<br><br>
> I found a reference to a similar problem here -<br><a href="http://qt-
project.org/forums/viewthread/47901" target="_blank">http://qt-
project.org/forums/viewthread/47901</a> - which was due to using<br>
> MOC on a network drive. In my case everything is on local SSD.<br><br>
> Any suggestions?<br><br>
> </blockquote>
> <div>Do you have the /MP flag set for your project?  Even though MOC 
takes longer, this will at least allow you to run one instance of MOC for every 
core on your system in addition to reducing build times in general.</div>
> </div>
> </div>
> 

    Maybe you have a shared floder and someone visits it at the same time you 
complie.