2

I've installed Visual Studio 2017 and QT 5.8.

Now I installed a QT-Add-in(from here) and I wanted to add the Path of QT 5.8 in Qt Options(in Visual Studio).

But I get an error like : "This QT version uses an unsupported makefile generator (used: MINGW, supported: MSVN.NET, MSBUILD)"

Is there a workaround or a way to fix this problem ?

Burkay
  • 91
  • 1
  • 1
  • 11

5 Answers5

2

The Qt that you're attempting to use has not been compiled with a binary-compatible compiler - either Visual Studio 2015 or Visual Studio 2017. You'll have to download Qt for MSVC2015, or build it yourself.

Kuba hasn't forgotten Monica
  • 95,931
  • 16
  • 151
  • 313
1

The think problem lies with what package you installed. I found, after I downloaded the add-in and downloaded the binaries, that I had downloaded the wrong binaries. What I did to fix the problem is I deleted my current installation of QT and reinstalled them (using QT's online installer) after unchecking the default MinGW binaries and checking the box for MSVC-2017-x64. Here is a picture, if that helps After installing that, I was able to correctly add the binaries to the path.

trevorist
  • 11
  • 1
1

The Qt Visual Studio Tools for VS2017 is now in Beta: https://blog.qt.io/blog/2017/08/03/qt-visual-studio-tools-version-2-1-2-beta/

It will be updated through the Visual Studio Marketplace from now on.

parsley72
  • 8,449
  • 8
  • 65
  • 98
0

My friend was suffering with qt because it does not work with visual studio 2017, today 08/14/2017 I downloaded the free version online, and in the components I unchecked MinGW and marked MSVC 2017 (But it only has the 64 bit version when I downloaded it today ).

Installation occurred normally and the result was this:

Simples teste com o qt utilizando o MSVC 2017

I wish good luck with your project, the version of qt I am using is 5.9.1

Samuel Ives
  • 302
  • 3
  • 14
0

I was able to get v2.2 to work on VS2017. However, when I closed Visual Studio and opened it up again, it did not work anymore. This is because VS upgraded the app to version 2.3 which did not work. I uninstalled 2.3, re-installed 2.2 and uncheck the auto update check box.

Adrian Hood Sr
  • 405
  • 5
  • 18