How to speed up Qt Windows Vc Build: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Add "cleanup" tag)
(Convert ExpressionEngine links)
Line 5: Line 5:
== Using /MP[processMax] option ==
== Using /MP[processMax] option ==


More information about /MP[processMax] option "here":http://msdn.microsoft.com/en-us/library/bb385193.aspx. Just add this flag to your spec file (''%QIDIR%/mkspecs/win32-msvc*/qmake.conf'').
More information about /MP[processMax] option [http://msdn.microsoft.com/en-us/library/bb385193.aspx here]. Just add this flag to your spec file (''%QIDIR%/mkspecs/win32-msvc*/qmake.conf'').


''processMax'' argument:
''processMax'' argument:
Line 16: Line 16:
== Using jom ==
== Using jom ==


In linux we do speed up with make -j4 or something like this. There is similar tool developed called jom, it can be downloaded from git "here":http://qt.gitorious.org/qt-labs/jom.
In linux we do speed up with make -j4 or something like this. There is similar tool developed called jom, it can be downloaded from git [http://qt.gitorious.org/qt-labs/jom here].


See also "jom's wiki page":jom
See also "jom's wiki page":jom


Precompiled packages can be found "here":http://get.qt.nokia.com/jom/.
Precompiled packages can be found [http://get.qt.nokia.com/jom/ here].


The original announcement of jom can be found "here":http://labs.qt.nokia.com/2009/03/27/speeding-up-visual-c-qt-builds/:
The original announcement of jom can be found [http://labs.qt.nokia.com/2009/03/27/speeding-up-visual-c-qt-builds/ here]:

Revision as of 15:00, 4 March 2015

This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine.
Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.

Using /MP[processMax] option

More information about /MP[processMax] option here. Just add this flag to your spec file (%QIDIR%/mkspecs/win32-msvc*/qmake.conf).

processMax argument:

  • (Optional) The maximum number of processes that the compiler can create.
  • The processMax argument must range from 1 through 65536. Otherwise, the compiler issues warning message D9014, ignores the processMax argument, and assumes the maximum number of processes is 1.
  • If you omit the processMax argument, the compiler retrieves the number of effective processors on your computer from the operating system, and creates a process for each processor.

Example: /MP2 (for dual core), /MP4 (for quad core)…

Using jom

In linux we do speed up with make -j4 or something like this. There is similar tool developed called jom, it can be downloaded from git here.

See also "jom's wiki page":jom

Precompiled packages can be found here.

The original announcement of jom can be found here: