Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
'nmake' is not recognized in the Qt command prompt?
When I run 'nmake' in the Qt command prompt, i get this:
"nmake is not recognized as an internal command, external command, program or batch file".
How come this happen? Why isn't 'nmake' recognized?
Have you installed the MS Visual C++ compiler? If not, you need to do it.
Also, you can try MSVS command prompt instead: it will have all the env set up (you just need to point it to Qt in PATH).
as sierdzio said you need a msvc compiler installed.
Visual studio provides you with a batch file were all necessary environment variables are already set. For msvc 2008 for example it is:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat
You may need to pass "x86" as an parameter to the script.
[quote author="sierdzio" date="1375433855"]Have you installed the MS Visual C++ compiler? If not, you need to do it.
Also, you can try MSVS command prompt instead: it will have all the env set up (you just need to point it to Qt in PATH).[/quote]
I have now installed Visual C++ compiler, but I get the same message:
“nmake is not recognized as an internal command, external command, program or batch file”.
You see I'm trying to follow these instructions in setting up KDSoap:
I thought I was supposed to stick to the Qt Command prompt when doing this, or could I also use MSVC command prompt? And if so where do I find it?
If I go to "Microsoft Visual Studio 2012->Visual Studio Tools" there are three types of command prompts. Can I use one of those?
!http://s13.postimg.org/v89got9pj/VS2012_x64_Croos_Tools_Command_Prompt.png(VS2012 x64 Croos Tools Command Prompt)!
Also, how do I point it to Qt in PATH? I guess I should do it in the PATH environment Variable (Start -> Control Panel -> System -> Advanced->Environment Variables), but how do I make the actual point to Qt?
Finally I made it. Installing KDSOAP - what a nightmare !!! =(
Now I only need to try it out, and hope this is the best part =)
Like you said it was a better idea to use mcvs command prompt instead, with all the necessary environment variables are already in place. It was the only thing that worked, and I guess any of the three command prompts will do but I used the VS2012 x64 Cross Tools Command Prompt.
Thanks for your replies and by the way forget about the Qt PATH question, later on it got obvious to me, and also I like the software Rapid Environment Editor.