Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. windeployqt, looks ok, but no files transferred
Forum Updated to NodeBB v4.3 + New Features

windeployqt, looks ok, but no files transferred

Scheduled Pinned Locked Moved Solved Installation and Deployment
80 Posts 4 Posters 22.9k Views 1 Watching
  • 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.
  • KroMignonK KroMignon

    @SPlatten said in windeployqt, looks ok, but no files transferred:

    I am constructing or trying to build an installer since I cannot get it working. On the target system Qt will not have been installed and shouldn't need installing, so I am trying to package up everything required to run the executable, thats why the plugins are being installed relative to the EXE.

    I understand this but, according to the console output, the application tries to load plugins from C:\Qt\Qt5.9.2\5.9.2\msvc2015\plugins:

    QFactoryLoader::QFactoryLoader() checking directory path "C:/Qt/Qt5.9.2/5.9.2/msvc2015/plugins/platforms"

    and not from the application path.

    So my question is why? This is not the normal case, you must have done something special.

    SPlattenS Offline
    SPlattenS Offline
    SPlatten
    wrote on last edited by
    #71

    @KroMignon , why is because I didn't realise it would do this, I thought the default search criteria for DLL's is first to look in the local folder then to search the Windows folder, I don't know how or why its looking in the Qt installation folder?

    Kind Regards,
    Sy

    KroMignonK 1 Reply Last reply
    0
    • KroMignonK KroMignon

      @SPlatten said in windeployqt, looks ok, but no files transferred:

      I am constructing or trying to build an installer since I cannot get it working. On the target system Qt will not have been installed and shouldn't need installing, so I am trying to package up everything required to run the executable, thats why the plugins are being installed relative to the EXE.

      I understand this but, according to the console output, the application tries to load plugins from C:\Qt\Qt5.9.2\5.9.2\msvc2015\plugins:

      QFactoryLoader::QFactoryLoader() checking directory path "C:/Qt/Qt5.9.2/5.9.2/msvc2015/plugins/platforms"

      and not from the application path.

      So my question is why? This is not the normal case, you must have done something special.

      SPlattenS Offline
      SPlattenS Offline
      SPlatten
      wrote on last edited by SPlatten
      #72

      @KroMignon Where does the qt.conf file go? In the same location as the EXE ?

      NVM, read from documentation.

      Kind Regards,
      Sy

      1 Reply Last reply
      0
      • SPlattenS SPlatten

        @KroMignon , why is because I didn't realise it would do this, I thought the default search criteria for DLL's is first to look in the local folder then to search the Windows folder, I don't know how or why its looking in the Qt installation folder?

        KroMignonK Offline
        KroMignonK Offline
        KroMignon
        wrote on last edited by KroMignon
        #73

        @SPlatten said in windeployqt, looks ok, but no files transferred:

        why is because I didn't realise it would do this, I thought the default search criteria for DLL's is first to look in the local folder then to search the Windows folder, I don't know how or why its looking in the Qt installation folder?

        The way Qt is searching plugins is well documented (cf. https://doc.qt.io/qt-5/deployment-plugins.html).
        This is why I asked you what you have done:

        • set QT_PLUGIN_PATH ?
        • defining a qt.conf file (cf. https://doc.qt.io/qt-5/qt-conf.html)?
        • by code with QCoreApplication::setLibraryPaths() or QCoreApplication::addLibraryPath()?

        It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

        SPlattenS 1 Reply Last reply
        0
        • KroMignonK KroMignon

          @SPlatten said in windeployqt, looks ok, but no files transferred:

          why is because I didn't realise it would do this, I thought the default search criteria for DLL's is first to look in the local folder then to search the Windows folder, I don't know how or why its looking in the Qt installation folder?

          The way Qt is searching plugins is well documented (cf. https://doc.qt.io/qt-5/deployment-plugins.html).
          This is why I asked you what you have done:

          • set QT_PLUGIN_PATH ?
          • defining a qt.conf file (cf. https://doc.qt.io/qt-5/qt-conf.html)?
          • by code with QCoreApplication::setLibraryPaths() or QCoreApplication::addLibraryPath()?
          SPlattenS Offline
          SPlattenS Offline
          SPlatten
          wrote on last edited by SPlatten
          #74

          @KroMignon , I've created local qt.conf:

          [Paths]
          Plugins=.
          

          This seems to have done the trick as the debug.txt reports the correct location is now being searched:

          QFactoryLoader::QFactoryLoader() checking directory path "C:/Users/simon.platten/Trainer/platforms" ...
          QFactoryLoader::QFactoryLoader() looking at "C:/Users/simon.platten/Trainer/platforms/qdirect2d.dll"
          Found metadata in lib C:/Users/simon.platten/Trainer/platforms/qdirect2d.dll, metadata=
          {
              "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
              "MetaData": {
                  "Keys": [
                      "direct2d"
                  ]
              },
              "className": "QWindowsDirect2DIntegrationPlugin",
              "debug": false,
              "version": 329986
          }
           
           
          Got keys from plugin meta data ("direct2d")
          QFactoryLoader::QFactoryLoader() looking at "C:/Users/simon.platten/Trainer/platforms/qminimal.dll"
          Found metadata in lib C:/Users/simon.platten/Trainer/platforms/qminimal.dll, metadata=
          {
              "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
              "MetaData": {
                  "Keys": [
                      "minimal"
                  ]
              },
              "className": "QMinimalIntegrationPlugin",
              "debug": false,
              "version": 329986
          }
           
           
          Got keys from plugin meta data ("minimal")
          QFactoryLoader::QFactoryLoader() looking at "C:/Users/simon.platten/Trainer/platforms/qoffscreen.dll"
          Found metadata in lib C:/Users/simon.platten/Trainer/platforms/qoffscreen.dll, metadata=
          {
              "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
              "MetaData": {
                  "Keys": [
                      "offscreen"
                  ]
              },
              "className": "QOffscreenIntegrationPlugin",
              "debug": false,
              "version": 329986
          }
           
           
          Got keys from plugin meta data ("offscreen")
          QFactoryLoader::QFactoryLoader() looking at "C:/Users/simon.platten/Trainer/platforms/qwindows.dll"
          Found metadata in lib C:/Users/simon.platten/Trainer/platforms/qwindows.dll, metadata=
          {
              "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
              "MetaData": {
                  "Keys": [
                      "windows"
                  ]
              },
              "className": "QWindowsIntegrationPlugin",
              "debug": false,
              "version": 329986
          }
           
           
          Got keys from plugin meta data ("windows")
          Cannot load library C:\Users\simon.platten\Trainer\platforms\qwindows.dll: Unknown error 0x000000c1.
          QLibraryPrivate::loadPlugin failed on "C:/Users/simon.platten/Trainer/platforms/qwindows.dll" : "Cannot load library C:\\Users\\simon.platten\\Trainer\\platforms\\qwindows.dll: Unknown error 0x000000c1."
          This application failed to start because it could not find or load the Qt platform plugin "windows"
          in "".
           
          Available platform plugins are: direct2d, minimal, offscreen, windows.
           
          Reinstalling the application may fix this problem.
          

          I've checked the that qwindows.dll is present, why can't it load the library?

          It looks like this error relates to the EXE architecture being not compatible, the EXE is win32. I thought I had transferred the correct DLL's for win32, will check again.

          Checked again, dll is the win32 version but still getting this message in the debug.txt ???

          Kind Regards,
          Sy

          KroMignonK 1 Reply Last reply
          0
          • SPlattenS SPlatten

            @KroMignon , I've created local qt.conf:

            [Paths]
            Plugins=.
            

            This seems to have done the trick as the debug.txt reports the correct location is now being searched:

            QFactoryLoader::QFactoryLoader() checking directory path "C:/Users/simon.platten/Trainer/platforms" ...
            QFactoryLoader::QFactoryLoader() looking at "C:/Users/simon.platten/Trainer/platforms/qdirect2d.dll"
            Found metadata in lib C:/Users/simon.platten/Trainer/platforms/qdirect2d.dll, metadata=
            {
                "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
                "MetaData": {
                    "Keys": [
                        "direct2d"
                    ]
                },
                "className": "QWindowsDirect2DIntegrationPlugin",
                "debug": false,
                "version": 329986
            }
             
             
            Got keys from plugin meta data ("direct2d")
            QFactoryLoader::QFactoryLoader() looking at "C:/Users/simon.platten/Trainer/platforms/qminimal.dll"
            Found metadata in lib C:/Users/simon.platten/Trainer/platforms/qminimal.dll, metadata=
            {
                "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
                "MetaData": {
                    "Keys": [
                        "minimal"
                    ]
                },
                "className": "QMinimalIntegrationPlugin",
                "debug": false,
                "version": 329986
            }
             
             
            Got keys from plugin meta data ("minimal")
            QFactoryLoader::QFactoryLoader() looking at "C:/Users/simon.platten/Trainer/platforms/qoffscreen.dll"
            Found metadata in lib C:/Users/simon.platten/Trainer/platforms/qoffscreen.dll, metadata=
            {
                "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
                "MetaData": {
                    "Keys": [
                        "offscreen"
                    ]
                },
                "className": "QOffscreenIntegrationPlugin",
                "debug": false,
                "version": 329986
            }
             
             
            Got keys from plugin meta data ("offscreen")
            QFactoryLoader::QFactoryLoader() looking at "C:/Users/simon.platten/Trainer/platforms/qwindows.dll"
            Found metadata in lib C:/Users/simon.platten/Trainer/platforms/qwindows.dll, metadata=
            {
                "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
                "MetaData": {
                    "Keys": [
                        "windows"
                    ]
                },
                "className": "QWindowsIntegrationPlugin",
                "debug": false,
                "version": 329986
            }
             
             
            Got keys from plugin meta data ("windows")
            Cannot load library C:\Users\simon.platten\Trainer\platforms\qwindows.dll: Unknown error 0x000000c1.
            QLibraryPrivate::loadPlugin failed on "C:/Users/simon.platten/Trainer/platforms/qwindows.dll" : "Cannot load library C:\\Users\\simon.platten\\Trainer\\platforms\\qwindows.dll: Unknown error 0x000000c1."
            This application failed to start because it could not find or load the Qt platform plugin "windows"
            in "".
             
            Available platform plugins are: direct2d, minimal, offscreen, windows.
             
            Reinstalling the application may fix this problem.
            

            I've checked the that qwindows.dll is present, why can't it load the library?

            It looks like this error relates to the EXE architecture being not compatible, the EXE is win32. I thought I had transferred the correct DLL's for win32, will check again.

            Checked again, dll is the win32 version but still getting this message in the debug.txt ???

            KroMignonK Offline
            KroMignonK Offline
            KroMignon
            wrote on last edited by
            #75

            @SPlatten said in windeployqt, looks ok, but no files transferred:

            It looks like this error relates to the EXE architecture being not compatible, the EXE is win32. I thought I had transferred the correct DLL's for win32, will check again.

            There is something very strange on your configuration.
            Are you sure you are using same Qt-Kit as kit used to build the binary?
            Can you run the binary with Qt Creator in release mode?

            It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

            SPlattenS 1 Reply Last reply
            0
            • KroMignonK KroMignon

              @SPlatten said in windeployqt, looks ok, but no files transferred:

              It looks like this error relates to the EXE architecture being not compatible, the EXE is win32. I thought I had transferred the correct DLL's for win32, will check again.

              There is something very strange on your configuration.
              Are you sure you are using same Qt-Kit as kit used to build the binary?
              Can you run the binary with Qt Creator in release mode?

              SPlattenS Offline
              SPlattenS Offline
              SPlatten
              wrote on last edited by
              #76

              @KroMignon , thats the odd thing...I can't even run it though Qt Creator in release mode, the only difference is that the message appears in a dialog...debug works fine.

              Kind Regards,
              Sy

              KroMignonK 1 Reply Last reply
              0
              • SPlattenS SPlatten

                @KroMignon , thats the odd thing...I can't even run it though Qt Creator in release mode, the only difference is that the message appears in a dialog...debug works fine.

                KroMignonK Offline
                KroMignonK Offline
                KroMignon
                wrote on last edited by
                #77

                @SPlatten said in windeployqt, looks ok, but no files transferred:

                thats the odd thing...I can't even run it though Qt Creator in release mode, the only difference is that the message appears in a dialog...debug works fine.

                This means you Qt Kit is corrupted... The only way would be to reinstall it, I guess or use a newer one.

                It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                SPlattenS 2 Replies Last reply
                0
                • KroMignonK KroMignon

                  @SPlatten said in windeployqt, looks ok, but no files transferred:

                  thats the odd thing...I can't even run it though Qt Creator in release mode, the only difference is that the message appears in a dialog...debug works fine.

                  This means you Qt Kit is corrupted... The only way would be to reinstall it, I guess or use a newer one.

                  SPlattenS Offline
                  SPlattenS Offline
                  SPlatten
                  wrote on last edited by SPlatten
                  #78

                  @KroMignon thank you, will see what can be done....for now I'm going to get it working using the debug libraries, I know these are ok, then the release dll's can be used later.

                  Kind Regards,
                  Sy

                  1 Reply Last reply
                  0
                  • KroMignonK KroMignon

                    @SPlatten said in windeployqt, looks ok, but no files transferred:

                    thats the odd thing...I can't even run it though Qt Creator in release mode, the only difference is that the message appears in a dialog...debug works fine.

                    This means you Qt Kit is corrupted... The only way would be to reinstall it, I guess or use a newer one.

                    SPlattenS Offline
                    SPlattenS Offline
                    SPlatten
                    wrote on last edited by
                    #79

                    @KroMignon , have got working release dll's and now it all works, thanks for your support.

                    Kind Regards,
                    Sy

                    KroMignonK 1 Reply Last reply
                    1
                    • SPlattenS SPlatten

                      @KroMignon , have got working release dll's and now it all works, thanks for your support.

                      KroMignonK Offline
                      KroMignonK Offline
                      KroMignon
                      wrote on last edited by
                      #80

                      @SPlatten said in windeployqt, looks ok, but no files transferred:

                      have got working release dll's and now it all works, thanks for your support.

                      nice to read :)

                      It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                      1 Reply Last reply
                      0

                      • Login

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