Skip to content
  • 3 Votes
    1 Posts
    No one has replied
  • 0 Votes
    1 Posts
    No one has replied
  • 0 Votes
    7 Posts

    OK, I rebuilt Qt 5.5.0 after removing the environment variables, but it unfortunately did not solve the problems I described.

    I was ultimately able to get the VS addin 1.2.4 working in VS 2013 by specifying the Qt installation as being at C:\Qt\5.5.0\qtbase instead of just C:\Qt\5.5.0. I was able to create a simple Qt GUI program and run both Debug and Release builds.

    But the remaining problem is that all Qt tools like designer, assistant, and linguist all crash as soon as they are started. In each case the event log holds an entry like this,

    Faulting application name: designer.exe, version:, time stamp: 0x55d4a1df
    Faulting module name: Qt5Gui.dll, version:, time stamp: 0x55d48d34
    Exception code: 0xc0000005
    Fault offset: 0x00000000006850f5
    Faulting process id: 0x5b8
    Faulting application start time: 0x01d0daadb7408ac1
    Faulting application path: C:\Qt\5.5.0\qtbase\bin\designer.exe
    Faulting module path: C:\Qt\5.5.0\qtbase\bin\Qt5Gui.dll
    Report Id: f504ee37-46a0-11e5-8267-8cdcd42c37a6
    Faulting package full name:
    Faulting package-relative application ID:

    So there is still some kind of issue with my build, though my simple Qt GUI project was evidently able to use Qt5Gui.dll without a problem.

    Any idea what could be causing this? Is there a problem with the configure options I chose? Or with the modifications I had to make to qcompilerdetection.h to get the build to work?


  • 0 Votes
    3 Posts


    Thanks for the reply. I was after something in between. I want to be able to specify the location of the .sln and the .vcxproj files. By default it does them inline with the qt sources, which gets very messy once VS starts building. I like how qt creator separates the source and build all together. [and by build i mean the object files as well as the makefiles/VS slns to build those objects].

    I couldn't find the option in the VS Addin so I got it working with something like this:

    qmake -tp vc -r -o ..\build\SOLUTION.sln

    It then built, in a folder outside source. I treat the SLN file as a temporary and just re-gen whenever I feel.

    Might help someone if they face the same problem.

  • 0 Votes
    1 Posts
    No one has replied