Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Qt 6.5.0 static Release libs overrides the Debug libs issue
QtWS25 Last Chance

Qt 6.5.0 static Release libs overrides the Debug libs issue

Scheduled Pinned Locked Moved Solved General and Desktop
7 Posts 3 Posters 473 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Cobra91151C Offline
    Cobra91151C Offline
    Cobra91151
    wrote on last edited by Cobra91151
    #1

    Hello!

    I have built Qt 6.5.0 static successfully first for Debug and then for Release mode. When I try to build my project in Debug mode it displays the following errors:

    link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /VERSION:1.1 /MANIFEST:embed /OUT:debug\WirelessManager.exe @C:\Users\cobra\AppData\Local\Temp\WirelessManager.exe.24860.10859.jom
    qrc_qstyle.cpp.obj : error LNK2005: "int __cdecl qInitResources_qstyle(void)" (?qInitResources_qstyle@@YAHXZ) already defined in qrc_qstyle.cpp.obj
    qrc_qstyle.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_qstyle(void)" (?qCleanupResources_qstyle@@YAHXZ) already defined in qrc_qstyle.cpp.obj
    qrc_qstyle1.cpp.obj : error LNK2005: "int __cdecl qInitResources_qstyle1(void)" (?qInitResources_qstyle1@@YAHXZ) already defined in qrc_qstyle1.cpp.obj
    qrc_qstyle1.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_qstyle1(void)" (?qCleanupResources_qstyle1@@YAHXZ) already defined in qrc_qstyle1.cpp.obj
    qrc_qmessagebox.cpp.obj : error LNK2005: "int __cdecl qInitResources_qmessagebox(void)" (?qInitResources_qmessagebox@@YAHXZ) already defined in qrc_qmessagebox.cpp.obj
    qrc_qmessagebox.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_qmessagebox(void)" (?qCleanupResources_qmessagebox@@YAHXZ) already defined in qrc_qmessagebox.cpp.obj
    qrc_qpdf.cpp.obj : error LNK2005: "int __cdecl qInitResources_qpdf(void)" (?qInitResources_qpdf@@YAHXZ) already defined in qrc_qpdf.cpp.obj
    qrc_qpdf.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_qpdf(void)" (?qCleanupResources_qpdf@@YAHXZ) already defined in qrc_qpdf.cpp.obj
    qrc_gui_shaders.cpp.obj : error LNK2005: "int __cdecl qInitResources_gui_shaders(void)" (?qInitResources_gui_shaders@@YAHXZ) already defined in qrc_gui_shaders.cpp.obj
    qrc_gui_shaders.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_gui_shaders(void)" (?qCleanupResources_gui_shaders@@YAHXZ) already defined in qrc_gui_shaders.cpp.obj
    qwindowsvistastyle.lib(main.cpp.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in appqlabel.obj
    qwindowsvistastyle.lib(main.cpp.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MTd_StaticDebug' in appqlabel.obj
    qwindowsvistastyle.lib(qwindowsvistastyle.cpp.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in appqlabel.obj
    qwindowsvistastyle.lib(qwindowsvistastyle.cpp.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MTd_StaticDebug' in appqlabel.obj
    qwindowsvistastyle.lib(cmake_pch.cxx.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in appqlabel.obj
    ...
    

    Full build log: https://mega.nz/file/RcZ0iQwD#eWuVp0UokNhXlyIwPhrK1OB252tUa2hqj3TjtSe3zuw
    When I compile Qt 6.5.0 for Debug/Release mode in separate folders it works well. The issue here is that Release build overrides the Debug build when I compile it in the same folder, for example: C:\QtStatic\6.5.0\msvc2022_64.

    I have tested it several times. This is clean Qt build without any additional libraries. I used the following commands:

    Debug:

    cmake.exe --trace-expand --trace-redirect=cmake.trace -DCMAKE_BUILD_TYPE="Debug" -DBUILD_SHARED_LIBS=OFF -DQT_BUILD_EXAMPLES=OFF -DINPUT_static_runtime=ON -DFEATURE_openssl_linked=OFF -DOPENSSL_USE_STATIC_LIBS=FALSE -DOPENSSL_MSVC_STATIC_RT=FALSE -DFEATURE_ltcg=OFF -DBUILD_qtwebengine=OFF -DCMAKE_INSTALL_PREFIX="C:\\QtStatic\\6.5.0\\msvc2022_64" -G Ninja C:\\QtBuild\\qt-everywhere-src-6.5.0
    

    Release:

    cmake.exe --trace-expand --trace-redirect=cmake.trace -DCMAKE_BUILD_TYPE="Release" -DBUILD_SHARED_LIBS=OFF -DQT_BUILD_EXAMPLES=OFF -DINPUT_static_runtime=ON -DFEATURE_openssl_linked=OFF -DOPENSSL_USE_STATIC_LIBS=FALSE -DOPENSSL_MSVC_STATIC_RT=FALSE -DFEATURE_ltcg=OFF -DBUILD_qtwebengine=OFF -DCMAKE_INSTALL_PREFIX="C:\\QtStatic\\6.5.0\\msvc2022_64" -G Ninja C:\\QtBuild\\qt-everywhere-src-6.5.0
    

    The Qt 6.5.0 static compilation process in both cases completes successfully but it seems that some Qt 6.5.0 Debug libraries gets overriden by Release libraries. Can anyone reproduce this issue? Is there a way to track down and solve this issue? Thank you.

    JoeCFDJ 1 Reply Last reply
    0
    • D DerReisende

      @Cobra91151 I don‘t think you can have both Release and Debug builds in the same PREFIX folder. Somewhere on the Qt website is a build instruction document how to build Qt and they mention a -debug-and-release flag - which only works for shared library builds but not for static. So I guess you have to use different locations.

      Cobra91151C Offline
      Cobra91151C Offline
      Cobra91151
      wrote on last edited by Cobra91151
      #7

      @DerReisende

      Hello!

      I have built successfully many Qt versions to the same install (PREFIX) directory. Also, it does not matter the shared or static builds. Additionally, Qt officially does compile/provide the debug/release builds to the same directory as well.

      I do not use this flag: -debug-and-release because I need to provide two different versions (Debug/Release) of additional libraries at once, for example: MySQL/OpenSSL/Zlib. So to make it simple, I compile it as separate builds. As you can read in my main post, the first goes for debug and then for release mode. I do not think the Qt 6.5.0 changes it because the default version for VS 2019 from for example: MaintenanceTool installs the debug/release builds in the same directory. So, this issue must be fixed. Thank you.

      1 Reply Last reply
      0
      • Cobra91151C Cobra91151

        Hello!

        I have built Qt 6.5.0 static successfully first for Debug and then for Release mode. When I try to build my project in Debug mode it displays the following errors:

        link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /VERSION:1.1 /MANIFEST:embed /OUT:debug\WirelessManager.exe @C:\Users\cobra\AppData\Local\Temp\WirelessManager.exe.24860.10859.jom
        qrc_qstyle.cpp.obj : error LNK2005: "int __cdecl qInitResources_qstyle(void)" (?qInitResources_qstyle@@YAHXZ) already defined in qrc_qstyle.cpp.obj
        qrc_qstyle.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_qstyle(void)" (?qCleanupResources_qstyle@@YAHXZ) already defined in qrc_qstyle.cpp.obj
        qrc_qstyle1.cpp.obj : error LNK2005: "int __cdecl qInitResources_qstyle1(void)" (?qInitResources_qstyle1@@YAHXZ) already defined in qrc_qstyle1.cpp.obj
        qrc_qstyle1.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_qstyle1(void)" (?qCleanupResources_qstyle1@@YAHXZ) already defined in qrc_qstyle1.cpp.obj
        qrc_qmessagebox.cpp.obj : error LNK2005: "int __cdecl qInitResources_qmessagebox(void)" (?qInitResources_qmessagebox@@YAHXZ) already defined in qrc_qmessagebox.cpp.obj
        qrc_qmessagebox.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_qmessagebox(void)" (?qCleanupResources_qmessagebox@@YAHXZ) already defined in qrc_qmessagebox.cpp.obj
        qrc_qpdf.cpp.obj : error LNK2005: "int __cdecl qInitResources_qpdf(void)" (?qInitResources_qpdf@@YAHXZ) already defined in qrc_qpdf.cpp.obj
        qrc_qpdf.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_qpdf(void)" (?qCleanupResources_qpdf@@YAHXZ) already defined in qrc_qpdf.cpp.obj
        qrc_gui_shaders.cpp.obj : error LNK2005: "int __cdecl qInitResources_gui_shaders(void)" (?qInitResources_gui_shaders@@YAHXZ) already defined in qrc_gui_shaders.cpp.obj
        qrc_gui_shaders.cpp.obj : error LNK2005: "int __cdecl qCleanupResources_gui_shaders(void)" (?qCleanupResources_gui_shaders@@YAHXZ) already defined in qrc_gui_shaders.cpp.obj
        qwindowsvistastyle.lib(main.cpp.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in appqlabel.obj
        qwindowsvistastyle.lib(main.cpp.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MTd_StaticDebug' in appqlabel.obj
        qwindowsvistastyle.lib(qwindowsvistastyle.cpp.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in appqlabel.obj
        qwindowsvistastyle.lib(qwindowsvistastyle.cpp.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MTd_StaticDebug' in appqlabel.obj
        qwindowsvistastyle.lib(cmake_pch.cxx.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in appqlabel.obj
        ...
        

        Full build log: https://mega.nz/file/RcZ0iQwD#eWuVp0UokNhXlyIwPhrK1OB252tUa2hqj3TjtSe3zuw
        When I compile Qt 6.5.0 for Debug/Release mode in separate folders it works well. The issue here is that Release build overrides the Debug build when I compile it in the same folder, for example: C:\QtStatic\6.5.0\msvc2022_64.

        I have tested it several times. This is clean Qt build without any additional libraries. I used the following commands:

        Debug:

        cmake.exe --trace-expand --trace-redirect=cmake.trace -DCMAKE_BUILD_TYPE="Debug" -DBUILD_SHARED_LIBS=OFF -DQT_BUILD_EXAMPLES=OFF -DINPUT_static_runtime=ON -DFEATURE_openssl_linked=OFF -DOPENSSL_USE_STATIC_LIBS=FALSE -DOPENSSL_MSVC_STATIC_RT=FALSE -DFEATURE_ltcg=OFF -DBUILD_qtwebengine=OFF -DCMAKE_INSTALL_PREFIX="C:\\QtStatic\\6.5.0\\msvc2022_64" -G Ninja C:\\QtBuild\\qt-everywhere-src-6.5.0
        

        Release:

        cmake.exe --trace-expand --trace-redirect=cmake.trace -DCMAKE_BUILD_TYPE="Release" -DBUILD_SHARED_LIBS=OFF -DQT_BUILD_EXAMPLES=OFF -DINPUT_static_runtime=ON -DFEATURE_openssl_linked=OFF -DOPENSSL_USE_STATIC_LIBS=FALSE -DOPENSSL_MSVC_STATIC_RT=FALSE -DFEATURE_ltcg=OFF -DBUILD_qtwebengine=OFF -DCMAKE_INSTALL_PREFIX="C:\\QtStatic\\6.5.0\\msvc2022_64" -G Ninja C:\\QtBuild\\qt-everywhere-src-6.5.0
        

        The Qt 6.5.0 static compilation process in both cases completes successfully but it seems that some Qt 6.5.0 Debug libraries gets overriden by Release libraries. Can anyone reproduce this issue? Is there a way to track down and solve this issue? Thank you.

        JoeCFDJ Offline
        JoeCFDJ Offline
        JoeCFD
        wrote on last edited by
        #2

        @Cobra91151 Add
        -DCMAKE_VERBOSE_MAKEFILE=ON
        to check which module build misses flag -g

        Cobra91151C 2 Replies Last reply
        0
        • JoeCFDJ JoeCFD

          @Cobra91151 Add
          -DCMAKE_VERBOSE_MAKEFILE=ON
          to check which module build misses flag -g

          Cobra91151C Offline
          Cobra91151C Offline
          Cobra91151
          wrote on last edited by
          #3

          @JoeCFD

          Ok. I will try it and reply later. Thank you.

          1 Reply Last reply
          0
          • JoeCFDJ JoeCFD

            @Cobra91151 Add
            -DCMAKE_VERBOSE_MAKEFILE=ON
            to check which module build misses flag -g

            Cobra91151C Offline
            Cobra91151C Offline
            Cobra91151
            wrote on last edited by Cobra91151
            #4

            @JoeCFD

            Good. I have built Qt 6.5.0 statically with this command: -DCMAKE_VERBOSE_MAKEFILE=ON and got the cmake trace files for Debug & Release modes.

            cmake_Debug.trace: https://mega.nz/file/4QoyFAhb#MYq4nbM08YTEqZhnUEBWAi2atAj2tPPO14sm4W30gN0
            cmake_Release.trace: https://mega.nz/file/dBIhRLoY#bEITaLweEq78TrBMP7Iq_XJzBmzBx171cu7FMYAzIjc

            I can not find any -g flags there. During Qt 6.5.0 static compilation I got the following output:

            ...
            [10502/10759] C:\PROGRA~1\MICROS~4\2022\ENTERP~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\cl.exe   /TP -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_UP_TO=0x040800 -DQT_EXPLICIT_QFILE_CONSTRUCTION_FROM_PATH -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_AS_CONST=1 -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_OPENGL_LIB -DQT_PLUGIN -DQT_QMLINTEGRATION_LIB -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_STATICPLUGIN -DQT_WARN_DEPRECATED_UP_TO=0x070000 -DUNICODE -DWIN32 -DWIN64 -D_CRT_SECURE_NO_WARNINGS -D_ENABLE_EXTENDED_ALIGNED_STORAGE -D_UNICODE -D_WIN64 -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtvirtualkeyboard\src\components\qtvkbcomponentsplugin_autogen\include -IC:\QtBuild\qt-everywhere-src-6.5.0\qtvirtualkeyboard\src\components -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtvirtualkeyboard\src\components -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtdeclarative\src\qml -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQml\6.5.0 -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQml\6.5.0\QtQml -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\src\corelib -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtCore\6.5.0 -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtCore\6.5.0\QtCore -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtCore -IC:\QtBuild\qt-everywhere-src-6.5.0\qtbase\mkspecs\win32-msvc -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQml -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQmlIntegration -IC:\QtBuild\qt-everywhere-src-6.5.0\qtdeclarative\src\qmlintegration -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtdeclarative\src\qmlintegration -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtNetwork -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtGui -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQuick -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQmlModels -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtOpenGL /DWIN32 /D_WINDOWS /DNDEBUG -O2 -std:c++17 -MT /W3 /EHs-c- /wd4530 /wd4577 -Zc:__cplusplus -permissive- -utf-8 -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:ternary -Zc:externConstexpr -Zc:wchar_t -bigobj -guard:cf -Gw /YuC:/QtBuild/qt-everywhere-src-6.5.0/qtBuild/qtvirtualkeyboard/src/components/CMakeFiles/qtvkbcomponentsplugin.dir/cmake_pch.hxx /FpC:/QtBuild/qt-everywhere-src-6.5.0/qtBuild/qtvirtualkeyboard/src/components/CMakeFiles/qtvkbcomponentsplugin.dir/./cmake_pch.cxx.pch /FIC:/QtBuild/qt-everywhere-src-6.5.0/qtBuild/qtvirtualkeyboard/src/components/CMakeFiles/qtvkbcomponentsplugin.dir/cmake_pch.hxx /showIncludes /Foqtvirtualkeyboard\src\components\CMakeFiles\qtvkbcomponentsplugin.dir\.rcc\qmlcache\qtvkbcomponentsplugin_KeyboardRow_qml.cpp.obj /Fdqtbase\qml\QtQuick\VirtualKeyboard\Components\qtvkbcomponentsplugin.pdb /FS -c C:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtvirtualkeyboard\src\components\.rcc\qmlcache\qtvkbcomponentsplugin_KeyboardRow_qml.cpp
            Microsoft (R) C/C++ Optimizing Compiler Version 19.35.32217.1 for x64
            Copyright (C) Microsoft Corporation.  All rights reserved.
            ...
            

            There is only -Gw flag but not -g? Thanks.

            Cobra91151C 1 Reply Last reply
            0
            • Cobra91151C Cobra91151

              @JoeCFD

              Good. I have built Qt 6.5.0 statically with this command: -DCMAKE_VERBOSE_MAKEFILE=ON and got the cmake trace files for Debug & Release modes.

              cmake_Debug.trace: https://mega.nz/file/4QoyFAhb#MYq4nbM08YTEqZhnUEBWAi2atAj2tPPO14sm4W30gN0
              cmake_Release.trace: https://mega.nz/file/dBIhRLoY#bEITaLweEq78TrBMP7Iq_XJzBmzBx171cu7FMYAzIjc

              I can not find any -g flags there. During Qt 6.5.0 static compilation I got the following output:

              ...
              [10502/10759] C:\PROGRA~1\MICROS~4\2022\ENTERP~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\cl.exe   /TP -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_UP_TO=0x040800 -DQT_EXPLICIT_QFILE_CONSTRUCTION_FROM_PATH -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_AS_CONST=1 -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_OPENGL_LIB -DQT_PLUGIN -DQT_QMLINTEGRATION_LIB -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_STATICPLUGIN -DQT_WARN_DEPRECATED_UP_TO=0x070000 -DUNICODE -DWIN32 -DWIN64 -D_CRT_SECURE_NO_WARNINGS -D_ENABLE_EXTENDED_ALIGNED_STORAGE -D_UNICODE -D_WIN64 -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtvirtualkeyboard\src\components\qtvkbcomponentsplugin_autogen\include -IC:\QtBuild\qt-everywhere-src-6.5.0\qtvirtualkeyboard\src\components -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtvirtualkeyboard\src\components -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtdeclarative\src\qml -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQml\6.5.0 -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQml\6.5.0\QtQml -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\src\corelib -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtCore\6.5.0 -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtCore\6.5.0\QtCore -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtCore -IC:\QtBuild\qt-everywhere-src-6.5.0\qtbase\mkspecs\win32-msvc -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQml -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQmlIntegration -IC:\QtBuild\qt-everywhere-src-6.5.0\qtdeclarative\src\qmlintegration -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtdeclarative\src\qmlintegration -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtNetwork -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtGui -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQuick -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtQmlModels -IC:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtbase\include\QtOpenGL /DWIN32 /D_WINDOWS /DNDEBUG -O2 -std:c++17 -MT /W3 /EHs-c- /wd4530 /wd4577 -Zc:__cplusplus -permissive- -utf-8 -FS -Zc:rvalueCast -Zc:inline -Zc:strictStrings -Zc:throwingNew -Zc:referenceBinding -Zc:ternary -Zc:externConstexpr -Zc:wchar_t -bigobj -guard:cf -Gw /YuC:/QtBuild/qt-everywhere-src-6.5.0/qtBuild/qtvirtualkeyboard/src/components/CMakeFiles/qtvkbcomponentsplugin.dir/cmake_pch.hxx /FpC:/QtBuild/qt-everywhere-src-6.5.0/qtBuild/qtvirtualkeyboard/src/components/CMakeFiles/qtvkbcomponentsplugin.dir/./cmake_pch.cxx.pch /FIC:/QtBuild/qt-everywhere-src-6.5.0/qtBuild/qtvirtualkeyboard/src/components/CMakeFiles/qtvkbcomponentsplugin.dir/cmake_pch.hxx /showIncludes /Foqtvirtualkeyboard\src\components\CMakeFiles\qtvkbcomponentsplugin.dir\.rcc\qmlcache\qtvkbcomponentsplugin_KeyboardRow_qml.cpp.obj /Fdqtbase\qml\QtQuick\VirtualKeyboard\Components\qtvkbcomponentsplugin.pdb /FS -c C:\QtBuild\qt-everywhere-src-6.5.0\qtBuild\qtvirtualkeyboard\src\components\.rcc\qmlcache\qtvkbcomponentsplugin_KeyboardRow_qml.cpp
              Microsoft (R) C/C++ Optimizing Compiler Version 19.35.32217.1 for x64
              Copyright (C) Microsoft Corporation.  All rights reserved.
              ...
              

              There is only -Gw flag but not -g? Thanks.

              Cobra91151C Offline
              Cobra91151C Offline
              Cobra91151
              wrote on last edited by
              #5

              Hello!

              I have reported this issue with Qt 6.5.0 static build here: https://bugreports.qt.io/browse/QTBUG-113260

              D 1 Reply Last reply
              0
              • Cobra91151C Cobra91151

                Hello!

                I have reported this issue with Qt 6.5.0 static build here: https://bugreports.qt.io/browse/QTBUG-113260

                D Offline
                D Offline
                DerReisende
                wrote on last edited by
                #6

                @Cobra91151 I don‘t think you can have both Release and Debug builds in the same PREFIX folder. Somewhere on the Qt website is a build instruction document how to build Qt and they mention a -debug-and-release flag - which only works for shared library builds but not for static. So I guess you have to use different locations.

                Cobra91151C 1 Reply Last reply
                0
                • D DerReisende

                  @Cobra91151 I don‘t think you can have both Release and Debug builds in the same PREFIX folder. Somewhere on the Qt website is a build instruction document how to build Qt and they mention a -debug-and-release flag - which only works for shared library builds but not for static. So I guess you have to use different locations.

                  Cobra91151C Offline
                  Cobra91151C Offline
                  Cobra91151
                  wrote on last edited by Cobra91151
                  #7

                  @DerReisende

                  Hello!

                  I have built successfully many Qt versions to the same install (PREFIX) directory. Also, it does not matter the shared or static builds. Additionally, Qt officially does compile/provide the debug/release builds to the same directory as well.

                  I do not use this flag: -debug-and-release because I need to provide two different versions (Debug/Release) of additional libraries at once, for example: MySQL/OpenSSL/Zlib. So to make it simple, I compile it as separate builds. As you can read in my main post, the first goes for debug and then for release mode. I do not think the Qt 6.5.0 changes it because the default version for VS 2019 from for example: MaintenanceTool installs the debug/release builds in the same directory. So, this issue must be fixed. Thank you.

                  1 Reply Last reply
                  0
                  • Cobra91151C Cobra91151 has marked this topic as solved on

                  • Login

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Users
                  • Groups
                  • Search
                  • Get Qt Extensions
                  • Unsolved