OK I did it. As I assumed the third party librarie has a deep impact of the QDebug-Infrastructure and catches all messages after the first time the library is used. There was no need to configure in QtCreator or something else except in the config of these other libraries. Now I get the messages back in the IDE Application Output. I hope that will help other poeple finding debugging problems.

Install a Qt message handler, set a breakpoint in there and take a look at the backtrace where it comes from.

I have included the import statement. I have my project being built two ways. I have it setup as using shared libs while debugging so I have a kit that is set up for that using the default qt install. I then have a static kit that I use for release. When I run the debug it loads fine, I get no errors. When I switch to the release kit I then get the error that you posted about an unknown component. Here is my qml file import QtQuick 2.12 import QtQuick.Window 2.12 import QtQuick.Extras 1.4 import QtQuick.Controls.Styles 1.4 Window { visible: true width: 640 height: 480 title: qsTr("Hello World") CircularGauge { id: gauge width: 400 height: 400 antialiasing: true tickmarksVisible: true anchors.horizontalCenter: parent.horizontalCenter anchors.verticalCenter: parent.verticalCenter value: 0 minimumValue: -100 maximumValue: 100 style: CircularGaugeStyle { minorTickmarkCount: 0 needle: Rectangle { y: outerRadius * 0.15 implicitWidth: outerRadius * 0.03 implicitHeight: outerRadius * 0.9 antialiasing: true color: Qt.rgba(0.66, 0.3, 0, 1) } } } } I just used the basic Qt Quick Application - Empty template for the project and only added CONFIG += static to the .pro file For some reason it's not finding the Controls.Styles using the static build. If I mouse over the import statement it reads 'Library at C:/Qt/Static/5.12.3/qml/QtQuick/Controls/Styles'.

@SGaist said in Win32 static linking?: Qt Creator architecture has nothing to do with the architecture of your application. To build a 32bit version of your application, use the 32bit package for MSVC2017. The same goes for the 64bit version. Yeah, that worked. When I tried it in 5.12.0 and failed, there must have been something misconfigured. I currently don't know for the static version, however when building the dynamic version you can say to configure that it should build dynamic backend selection. Following some info from another post, I tried the following configure.bat options: -prefix "C:\Qt\Qt5.12.2\5.12.2\msvc2017sr" -release -platform win32-msvc -confirm-license -opensource -nomake examples -nomake tests -static -static-runtime -opengl dynamic -angle -combined-angle-lib -no-feature-d3d12 Now it works on the 32-bit Windows machine I used to build Qt and the application (and still works fine on the 64-bit machine I can also build it on), but when I run it on another Win7 64-bit machine that has never had Qt installed on it, I just get the window frame again. Is it looking for a DLL? I only have a nebulous idea of what some of those configure options actually mean, so I don't know what to try next.

No problem. Good luck with your project!

Dear All: here is my situation The class which cause compile Error is PropertyColumnMapping in DynamicObjectCore.pro Then CommonBusiness.pro using this class And Presentation linked to both CommonBusiness.pro & DynamicObjectCore.pro Clean + QMake + Rebuild doesn't work. Here is my Project Structure. Application.pro TEMPLATE = subdirs CONFIG += ordered SUBDIRS += Framework Services Business Presentation Updater QT += qml quick widgets network sql xml Business.pro TEMPLATE = subdirs SUBDIRS += CommonBusiness ServiceBusiness //Link to Framework.System CommonBusiness.pro QT -= gui QT += qml quick sql xml xmlpatterns network TARGET = CommonBusiness TEMPLATE = lib CONFIG += staticlib c++11 SOURCES += commonbusiness.cpp ... HEADERS += commonbusiness.h ... //# Link to FrameWork.DynamicObjectCore DynamicObjectCore.pro QT -= gui QT += qml TARGET = DynamicObjectCore TEMPLATE = lib CONFIG += staticlib c++11 #DEFINES += DYNAMICOBJECTCORE_LIBRARY SOURCES += MetadataModel/propertycolumnmapping.cpp ... HEADERS += MetadataModel/propertycolumnmapping.h ... unix { target.path = /usr/lib INSTALLS += target } Presentation.pro TEMPLATE = app TARGET = [ApplicationName] QT += qml quick widgets network sql xml xmlpatterns //# for QT 5.4 qtHaveModule(webengine) { QT += webengine DEFINES += QT_WEBVIEW_WEBENGINE_BACKEND } qtHaveModule(webkitwidgets) { QT += webkitwidgets } //# for QT 5.7 equals(QT_VERSION, QT_VERSION_CHECK(5, 7, 0)) { QT += webview DEFINES += QT_WEBVIEW_CONTROL_BACKEND } CONFIG += c++11 CONFIG(release, debug|release) { CONFIG += release force_debug_info } RESOURCES += qml.qrc shared.qrc //# Link to DynamicObjectCore //# Link to CommonBusiness

@SGaist This is so new and fresh, I love it. I'll consider making a few pull requests in the near future. :)

Then there might be something I'm missing about your current setup. In any case, take a look at this excellent blog article about that subject. That should give you the clues needed to solve your situation.

Thank You! Not a silly question. Actually, I upgraded my version of VS from 2012 to 2013 to go with Qt for MSVC2013. Otherwise, I wouldn't even be able to compile pure C++ with Qt, which I have had no problem doing. I just can't seem to create even a pure C++ library in VS OR Qt, and have Qt recognize it. That will be my challenge in the next days, and is understandably slightly off-topic for this thread. But I will definitely report back. Thanks to all!

@Mark81 No problem.

I'll try that, thanks for the help.

@mbnoimi Ok, why if I can ask?

Does anyone have instructions for Qt static build that is version 5.4 or greater?

So I finally found a part in the documentation saying: PRE_TARGETDEPS Lists libraries that the target depends on. Some backends, such as the generators for Visual Studio and Xcode project files, do not support this variable. Generally, this variable is supported internally by these build tools, and it is useful for explicitly listing dependent static libraries. Apparently I have to include the lib manually in the .xcodeproj file. That worked, but isn't Add Library... supposed to add the necessary commands to the .pro file?

But this time, I have a different error: /home/kumararajas/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: /home/kumararajas/Integrate_UI/G-CPU/lib/libuicorelib.a(uicontroller.o): undefined reference to symbol '__cxa_begin_catch@@CXXABI_1.3' /home/kumararajas/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: note: '__cxa_begin_catch@@CXXABI_1.3' is defined in DSO /home/kumararajas/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/../arm-linux-gnueabihf/libc/lib/arm-linux-gnueabihf/libstdc++.so.6 so try adding it to the linker command line /home/kumararajas/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/../arm-linux-gnueabihf/libc/lib/arm-linux-gnueabihf/libstdc++.so.6: could not read symbols: Invalid operation collect2: error: ld returned 1 exit status make[4]: *** [bin/FireApp] Error 1 make[3]: *** [libraries] Error 2 make[2]: *** [libraries] Error 2 make[1]: *** [libraries] Error 2 This looks like standard library compatibility issue. Any thoughts on this?

Hi, To add to @koahnig , this article explains very well how to setup dependencies efficiently

@moozoom I run in the same paradigm when I try to create a static linked library with Qt targeting Android and latter to use it with JINI on Android Studio. Reading you post I see you have almost the same problem like me with one difference. To me are working as far I use only std library My problem appears when I use QString for example in the library. Looks the static build does not statically includes the Qt framework dependencies. Finally did you find a solution? Me I run with this issue past over one month. Thanks