1b031630de
of course all helper libraries are built statically, so the criterion is not useful. what is interesting is whether the whole qt configuration is static, as that determines what will happen with the helper library when linking the final "actual" artifacts. Change-Id: I96980c645cb478b2f7a30688b49cb51bec8c9f08 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com> Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
28 lines
697 B
Plaintext
28 lines
697 B
Plaintext
#
|
|
# W A R N I N G
|
|
# -------------
|
|
#
|
|
# This file is not part of the Qt API. It exists purely as an
|
|
# implementation detail. It may change from version to version
|
|
# without notice, or even be removed.
|
|
#
|
|
# We mean it.
|
|
#
|
|
|
|
load(qt_build_paths)
|
|
|
|
TEMPLATE = lib
|
|
CONFIG -= qt
|
|
|
|
contains(QT_CONFIG, debug_and_release): CONFIG += debug_and_release
|
|
contains(QT_CONFIG, build_all): CONFIG += build_all
|
|
|
|
DESTDIR = $$MODULE_BASE_OUTDIR/lib
|
|
DLLDESTDIR = $$MODULE_BASE_OUTDIR/bin
|
|
|
|
# In static builds of Qt, convenience libraries must be installed,
|
|
# as in this case they are not linked to the final library/plugin.
|
|
installed|contains(QT_CONFIG, static): load(qt_installs)
|
|
|
|
TARGET = $$qtLibraryTarget($$TARGET)
|