Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Make Build Error in Windows.
QtWS25 Last Chance

Make Build Error in Windows.

Scheduled Pinned Locked Moved Qt Creator and other tools
4 Posts 3 Posters 7.1k 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.
  • AlicemirrorA Offline
    AlicemirrorA Offline
    Alicemirror
    wrote on last edited by
    #1

    Hi to all,

    I have setup a Qt-SDK environment under windows to recompile a developed project created under linux (where it works fine)

    For organization questions I installed the Qt environment in a clean machine using a different disk from C: (it's E:)
    Then, - as I have done in other cases with the QT Sdk installed in C:\ - I ported the linux project under windows to start building. Removed the .user files and checked the debug/release paths in the projects scree of Qt-Creator.

    Starting the compilation (with or without the shadow-build option) all works fine while at the end I get the error

    @Starting: "E:\QtSDK\mingw\bin\mingw32-make.exe" -w
    mingw32-make: Entering directory C:/QTDevel/RCHobbyStream' E:/QtSDK/mingw/bin/mingw32-make -f Makefile.Debug mingw32-make[1]: Entering directory C:/QTDevel/RCHobbyStream'
    Copying application data...
    0 File(s) copied
    mingw32-make[1]: Leaving directory C:/QTDevel/RCHobbyStream' mingw32-make: Leaving directory C:/QTDevel/RCHobbyStream'
    Cannot perform a cyclic copy
    mingw32-make[1]: *** [copydeploymentfolders] Error 4
    mingw32-make: *** [debug] Error 2
    The process "E:\QtSDK\mingw\bin\mingw32-make.exe" exited with code 2.
    Error while building project RCHobbyStream (target: Desktop)
    When executing build step 'Make'@

    Seeing in the debug or release folder, as a matter of fact I see that the .exe file was built.

    Trying to launch it stand-alone (outside from the Qt-creator environment) the program don't start while I set in the same directory all the DLLs and components needed (probably because these are on the E:\QT-SDK folder). Then, the program starts but don't work. But this is a secondary problem.

    I have no idea if this kind of installation is possible and works, or if I should re-create a standard installation of Qt-SDK on a clean machine, using the C: disk. Or if it is something different...

    Enrico Miglino (aka Alicemirror)
    Balearic Dynamics
    Islas Baleares, Ibiza (Spain)
    www.balearicdynamics.com

    1 Reply Last reply
    0
    • A Offline
      A Offline
      andre
      wrote on last edited by
      #2

      Installing on E should not be a problem in and off itself. I use non-standard paths for Qt all the time. As long as you directly install into/build into that directory, you should be fine. Qt can, AFAIK, not be moved to a new directory.

      1 Reply Last reply
      0
      • AlicemirrorA Offline
        AlicemirrorA Offline
        Alicemirror
        wrote on last edited by
        #3

        Andre,

        sure, I don't moved Qt anyway!!!
        The problem is that after Installing (and working) under windows with Qt installed in E:\QT-SDK the same Qt-Quick project that works on Linux when I copy to E:\QT-Devel directory, remove the .user file and load from windows Qt-Creator, I get always this error.
        Is there some other parameter that I don't know that should be changed, out of the "project" configuration page in Qt-Creator? The returned error (I posted it integrally) is not so clear to investigate on what is the folder that is not found. The difference I see is that QML elements (the main.qml and its qml folder) are not copied during make, as I see in the Qt-Build-Desktop folder of linux.

        Enrico Miglino (aka Alicemirror)
        Balearic Dynamics
        Islas Baleares, Ibiza (Spain)
        www.balearicdynamics.com

        1 Reply Last reply
        0
        • U Offline
          U Offline
          ubuuntu
          wrote on last edited by
          #4

          It's been a while, but this problem still persists. If you delete the original *.pro.user file then import project, this problem is still there.

          The trick is to enable shadow build in the Target setup screen when importing the project. This will create separate target directories which appear to be expected by the deplyment script.

          Hope this will help somebody.

          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