Difference between revisions of "How to prevent Qt from compiling code examples"

From Qt Wiki
Jump to: navigation, search
Line 11: Line 11:
 
To make it much quicker, an easy way is to prevent examples from being compiled.
 
To make it much quicker, an easy way is to prevent examples from being compiled.
  
One way of doing it is:<br />* extract source sdk (or git clone it)<br />* start configure with option &quot;dont-process&amp;quot; (works only on windows, doesn't seem to exist on Linux configure)<br /><code><br />configure -openssl -qt-libjpeg -qt-gif -qt-zlib -webkit -phonon -no-plugin-manifests -plugin-sql-sqlite -opensource -debug-and-release -confirm-license -dont-process<br /></code><br />* then launch explicitely newly created qmake to build only libs and tools<br /><code><br />QTDIR%/qmake/qmake -r QT_BUILD_PARTS=&quot;libs tools&amp;quot;<br /></code><br />* Compile generated makefile<br /><code><br />nmake<br /></code>
+
One way of doing it is:
<br />Compilation time is improved by around 80 (approximately 100 minutes instead of 8 hours) and you end up with a perfectly usable Qt, in debug and release.
+
* extract source sdk (or git clone it)
 +
* start configure with option "dont-process" (works only on windows, doesn't seem to exist on Linux configure)
 +
<code>
 +
configure -openssl -qt-libjpeg -qt-gif -qt-zlib -webkit -phonon -no-plugin-manifests -plugin-sql-sqlite -opensource -debug-and-release -confirm-license -dont-process
 +
</code>
 +
* then launch explicitely newly created qmake to build only libs and tools
 +
<code>
 +
QTDIR%/qmake/qmake -r QT_BUILD_PARTS="libs tools"
 +
</code>
 +
* Compile generated makefile
 +
<code>
 +
nmake
 +
</code>
  
On Linux configure and build can be accelerated by using all available cores.<br /><code><br />export MAKEFLAGS=-j4<br />configure -AllTheOptionsYouNeed<br />make -j4<br /></code>
+
Compilation time is improved by around 80 (approximately 100 minutes instead of 8 hours) and you end up with a perfectly usable Qt, in debug and release.
  
Note that compilation place is hardcoded inside qmake and used to find QMAKESPECs. You can however change it later using<br /><code><br />qmake -query<br />lists all available variable (mostly paths)<br />qmake -set<br />overrides previously hardcoded value
+
On Linux configure and build can be accelerated by using all available cores.
 +
<code>
 +
export MAKEFLAGS=-j4
 +
configure -AllTheOptionsYouNeed
 +
make -j4
 +
</code>
 +
 
 +
Note that compilation place is hardcoded inside qmake and used to find QMAKESPECs. You can however change it later using
 +
<code>
 +
qmake -query
 +
lists all available variable (mostly paths)
 +
qmake -set
 +
overrides previously hardcoded value

Revision as of 10:21, 25 February 2015

English Български

NOTE: This guide is for Qt 4. See Building_Qt_5_from_Git for instructions for Qt 5.

Compile Qt Faster by Skipping Examples

Compiling Qt is fairly straight-forward, but quite a lengthy process.

To make it much quicker, an easy way is to prevent examples from being compiled.

One way of doing it is:

  • extract source sdk (or git clone it)
  • start configure with option "dont-process" (works only on windows, doesn't seem to exist on Linux configure)

configure -openssl -qt-libjpeg -qt-gif -qt-zlib -webkit -phonon -no-plugin-manifests -plugin-sql-sqlite -opensource -debug-and-release -confirm-license -dont-process

  • then launch explicitely newly created qmake to build only libs and tools

QTDIR%/qmake/qmake -r QT_BUILD_PARTS="libs tools"

  • Compile generated makefile

nmake

Compilation time is improved by around 80 (approximately 100 minutes instead of 8 hours) and you end up with a perfectly usable Qt, in debug and release.

On Linux configure and build can be accelerated by using all available cores. export MAKEFLAGS=-j4 configure -AllTheOptionsYouNeed make -j4

Note that compilation place is hardcoded inside qmake and used to find QMAKESPECs. You can however change it later using qmake -query lists all available variable (mostly paths) qmake -set overrides previously hardcoded value