summaryrefslogtreecommitdiffstats
path: root/src/3rdparty/libgq/gconf/gconfitem.cpp
diff options
context:
space:
mode:
authorAlexey Edelev <alexey.edelev@qt.io>2021-06-10 19:01:35 +0200
committerAlexey Edelev <alexey.edelev@qt.io>2021-06-16 16:58:45 +0200
commit5fb99e3860eb43f4bacacec7f4a4626cb0159b14 (patch)
tree5f521fbb62d9408d42b3325e831eff5489eb78a0 /src/3rdparty/libgq/gconf/gconfitem.cpp
parent1f4b237dade9d0d2ed5439e3834ac22985797561 (diff)
Check the impact of static link order for user projectsHEADdev
For user projects we run the static link order check once 'find_package(Qt6 ...)' is called. If linker can resolve circular dependencies between static libraries and object files we set the _qt_link_order_matters property of the Qt::Platform target. This indicates the use of finalizers is not required and we may rely on CMake-base propagation of resource libraries and resource object files. If linker could not resolve circular dependencies depending on the _qt_resource_objects_finalizer_mode value: - Finalizer will be called and collected resource objects will be linked to the target directly. - Finalizer will be omitted and resource objects will be linked using the target_sources function implicitly. This only propagates resource one level up if consumer links the static library PUBLICly, but all symbols will be resolved correctly since object files are placed in the beginning of the linker line. In the CMake version 3.21 we expect that CMake will take care about the order of the resource object files in a linker line, it's expected that all object files are located at the beginning of the linker line. TODO: Need to confirm that the CMake 3.21 meets the expectations. Amends 4e901a2f99cbfda3b479253ea54b16f02e1c3aa5 Pick-to: 6.2 Task-number: QTBUG-93002 Task-number: QTBUG-94528 Change-Id: Ia68976df8182d3d3007b90c475c1e3928a305339 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Diffstat (limited to 'src/3rdparty/libgq/gconf/gconfitem.cpp')
0 files changed, 0 insertions, 0 deletions