'cl' is not recognized



  • any one knows why I get this error message
    'cl' is not recognized as an internal or external command,
    operable program or batch file.

    TIA



  • You are getting that error because the Microsoft compiler (cl.exe) is not in the PATH



  • Thank you for your prompt reply, which the following folders should be the one that Qt needs to know about?
    If Qt provides an installer with MinGW, why not provide one with "Windows SDK":http://www.microsoft.com/en-us/download/details.aspx?id=23719. It would certainly rebuild the trust of VC++ developers.

    D:\Qt\Qt5.3.1\5.3\Src\qtwebkit\Tools\vcbin\cl.exe
    C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\cl.exe
    C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\x86_amd64\cl.exe

    TIA



  • MSVC++ is not free. It is licensed. Qt can't distribute. Put your VC++ environment in to path. Try with C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\cl.exe. It may fail for other libraries as well. Also you can hit google/qt wiki on how to setup Qt for Visual Studio. It should be straight forward.



  • The SDK *is free and MSVC++ is part of the SDK. I am sure Qt can cut a deal with MS to let them use their *free SDK to be incorporated with the Qt installer. It would even give MS more exposure on their GUI toolkit, while at the same time keeping Qt on its toes. But I guess WPF is way too much of a threat to Qt Quick for Qt to even consider this step. Humm, I suspect that we will not be seeing the coupling of Qt and Windows SDK any time soon.
    For MS is not a good deal either, since most programmers choose Qt when running away from C# and the madness of C++/CLI, which BTW should either be discontinued or be used as a replacement of C#, and then truly say... a better C++.

    Thanks dues, I have solve the problem with cl.exe, but now I have a problem with "jom":http://qt-project.org/forums/viewthread/46106/. Brr


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.