qtwindows-10windows-10-desktop

Installing a compiler for Qt4.8.7 on Windows10


I am trying to install Qt4.8.7 for Windows 10 and I am having some issues with installing the corresponding compiler.

I got the Qt4.8.7 installer from this link: https://download.qt.io/archive/qt/4.8/4.8.7/ and I have tried working with the MSVC2010 and the mingw versions. For the MSVC2010 version, I followed this guide https://wiki.qt.io/How_to_setup_MSVC2010 (with a lot of dead links) and installed the compiler alongside the MSVC service pack 1 and Windows SDK 7.1. I have not been able to find an installer for Visual Studio 2010 or the VS service pack 1. Qt studio recognises the version of qt I have installed alongside the corresponding MSVC2010 x86 compiler but when I compile I get this error for a missing header: "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\intrin.h:26: error: C1083: Cannot open include file: 'ammintrin.h': No such file or directory".

For the mingw version, I have not been able to find the correct version "mingw482" and other versions I have tried do not seem to be compatible. I have tried mingw installer programs as well as using the QT online installer to try and find the correct version but I haven't had much luck when compiling.

Has anyone got qt4.8.7 running on windows recently? If so, could you please point me in the right direction for installing the correct compiler?

Many thanks.


Solution

  • Here a short description for getting it to work with Visual Studio 2008 and the newest Qt Creator 4.13.

    You will need:

    Steps (all absolute paths are standard installation paths):

    Now you should be able to compile your project from Qt Creator and Qt-colored-commandline. For integration of MSVC 9.0 into Visual Studio 2015 and newer you will also need to install Visual Studio 2012 Express. In that order:

    1. VS2008
    2. VS2012 (Here MS programmed in some magic so newer VS can see older build tools)
    3. VS201x

    It could work in any other order but don't rely on it. Also it could just flat out not work and you will waste a week of your life to fix it; but then it will work.

    Haven't tested it but I could imagine the same workflow will work for VS2010.