How to prevent Qt from compiling code examples: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AutoSpider (talk | contribs) (Add "cleanup" tag) |
||
Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
'''English''' [[How_to_prevent_Qt_from_compiling_code_examples_Bulgarian|Български]] | '''English''' [[How_to_prevent_Qt_from_compiling_code_examples_Bulgarian|Български]] | ||
Revision as of 16:01, 3 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. |
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