The problem of QtCreator on win
-
In Windows your able to read out the path and check for yourself. It should have set the path automatic when installing. Did you have other MSVC compilers installed before? Maybe remove the old version from you path so it will find the new one?
@Jeroentjehome Sometimes, I go back home for a computer to open, and then every 2 days in the cl.exe to find out the error of the command of the computer, can be compiled, but it will be the same error, the recent emergence of information, whether it can help to solve the error?
-
Hi,
In your last post you mention that the cl sometimes works and sometimes not? Or am I mistaken?
It might be good that when you encounter this error you do a clean/run qmake/ build. Or just delete the entire 'release' shadow build folder. -
Hi,
In your last post you mention that the cl sometimes works and sometimes not? Or am I mistaken?
It might be good that when you encounter this error you do a clean/run qmake/ build. Or just delete the entire 'release' shadow build folder.@Jeroentjehome I just tried to delete the build folder, the original notebook computer is still unable to compile, but after the replacement of the desktop, the compiler normal.
-
Hmm,
Well, then it seems that something must have gone wrong when you installed the notebook. Maybe reinstall MSVC and Qt and that might fix it.
Good for you that you are able to compile! -
Hmm,
Well, then it seems that something must have gone wrong when you installed the notebook. Maybe reinstall MSVC and Qt and that might fix it.
Good for you that you are able to compile!@Jeroentjehome Thank you. I'll try.
-
Hmm,
Well, then it seems that something must have gone wrong when you installed the notebook. Maybe reinstall MSVC and Qt and that might fix it.
Good for you that you are able to compile!@Jeroentjehome Sorry, I have tried to reinstall the Qt environment, is still invalid, online has said that the path to join the environmental variables PATH, QtCeator can not automatically identify the compiler path? I didn't join in before.
-
Hmm,
Well, then it seems that something must have gone wrong when you installed the notebook. Maybe reinstall MSVC and Qt and that might fix it.
Good for you that you are able to compile!@Jeroentjehome Set the path to the PATH CL environment variable, or not.
-
Hmm,
Well, then it seems that something must have gone wrong when you installed the notebook. Maybe reinstall MSVC and Qt and that might fix it.
Good for you that you are able to compile!@Jeroentjehome Will it be caused by MSVC2014? Can I from the QtCreator "build and run" setting, I use the Qt compiler settings is MSVC2013 ah.
-
Hi,
Yes it is, on Windows you can't mix and match. All of your libraries/application must be compiled with the same compiler. They are not compatible one with the other. So since you have the VS2013 package installed you must use Visual Studio 2013.
If you want to use Visual Studio 2015, you have to build Qt yourself at this time.
-
Hi,
Yes it is, on Windows you can't mix and match. All of your libraries/application must be compiled with the same compiler. They are not compatible one with the other. So since you have the VS2013 package installed you must use Visual Studio 2013.
If you want to use Visual Studio 2015, you have to build Qt yourself at this time.
@SGaist said:
Visual Studio 2015 is installed to my experience, my computer at the same time the installation of Visual Studio 2015 and Visual Studio 2013, QtCreator can automatically identify it? -
I'm not sure I understood what you wrote. Do you have both version installed on your machine ?
-
I'm not sure I understood what you wrote. Do you have both version installed on your machine ?
@SGaist Qt has MSVC 32 and x64, both use msvc2013 compiler, the compiler also installed vs2013 and 2015 (for experience). Mingw version can be compiled, MSVC is unable to find the CL command.
-
Did you check that your kits are setup properly ?
-
@SGaist said:
Did you check that your kits are setup properly ?
Check the version of the Qt and the compiler's information from the setup to check for exceptions
-
Do you have any warnings ?
-
@SGaist No warning from the setup interface, now use the MinGW are all normal
