make it possible to explicitly suppress the qml import scan
if the user knows that no additional imports need to be linked, this can be used to optimize the build time. as it happens, it can also be used to fix the build of the qml tools themselves ... Change-Id: Id77aea1f20cabdc2e831540c61d8a4b8e85c040b Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
This commit is contained in:
parent
c057e23b02
commit
21ce4fd240
@ -74,7 +74,8 @@ wince*:static:gui {
|
||||
}
|
||||
|
||||
# static builds: link qml import plugins into the app.
|
||||
if(contains(QT, qml)|contains(QT_PRIVATE, qml)):contains(QT_CONFIG, static):contains(TEMPLATE, .*app):!host_build {
|
||||
if(contains(QT, qml)|contains(QT_PRIVATE, qml)): \
|
||||
contains(QT_CONFIG, static):contains(TEMPLATE, .*app):!host_build:!no_import_scan {
|
||||
# run qmlimportscanner
|
||||
qtPrepareTool(QMLIMPORTSCANNER, qmlimportscanner)
|
||||
exists($$QMLIMPORTSCANNER) {
|
||||
|
Loading…
Reference in New Issue
Block a user