Uploaded image for project: 'Qt Creator'
  1. Qt Creator
  2. QTCREATORBUG-7973

'cl' is not recognized as an internal or external command

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Not Evaluated
    • None
    • Qt Creator 2.4.1, Qt Creator 2.6.0-beta
    • None
    • Windows XP 2003 Professional 32-bit
      Service Pack 3
      msvc2008

      Qt Creator 2.5.82 (2.6.0-beta) - have tested with 2.4.1 as well
      From revision 66a19cc457 (binary package qt-creator-windows-2.5.82-233-2012-09-11_00-02-15)

    Description

      Following on from this, Qt Creator can't seem to find cl.exe, even with the appropriate initialisation script. See attached screenshots for more Creator environment info.

      Steps to reproduce:

      1. File > New File or Project... > Non-Qt Project > Plain C++ Project
      2. Build Project

      The build fails:

      13:40:12: Running steps for project cl-test...
      13:40:12: Starting: "C:\Dev\qtbase-debug\bin\qmake.exe" C:\Dev\test\cl-test\cl-test.pro -r -spec win32-msvc2008 "CONFIG+=qml_debug"
      13:40:13: The process "C:\Dev\qtbase-debug\bin\qmake.exe" exited normally.
      13:40:13: Starting: "C:\Dev\qt-creator-windows-2.5.82-233-2012-09-11_00-02-15\bin\jom.exe" 
      	C:\Dev\qt-creator-windows-2.5.82-233-2012-09-11_00-02-15\bin\jom.exe -f Makefile.Debug
      	cl -c -nologo -Zm200 -Zc:wchar_t -Zi -MDd -GR -W3 -w34100 -w34189 -EHsc -DUNICODE -DWIN32 -DQT_QML_DEBUG -I"..\..\qtbase-debug\mkspecs\win32-msvc2008" -Fodebug\ @C:\DOCUME~1\Mitch!\LOCALS~1\Temp\main.obj.5992.16.jom
      'cl' is not recognized as an internal or external command,
      operable program or batch file.
      jom: C:\Dev\test\cl-test\Makefile.Debug [debug\main.obj] Error 1
      jom: C:\Dev\test\cl-test\Makefile [debug] Error 2
      13:40:13: The process "C:\Dev\qt-creator-windows-2.5.82-233-2012-09-11_00-02-15\bin\jom.exe" exited with code 2.
      Error while building/deploying project cl-test (target: msvc-qtbase)
      When executing step 'Make'
      

      Build environment in Creator:

      C:\Dev\qtbase-debug\bin;C:\Dev\qt-creator-windows-2.5.82-233-2012-09-11_00-02-15\bin;C:\Dev\Perl\site\bin;C:\Dev\Perl\bin;C:\Dev\MinGW\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\jEdit;C:\Program Files\doxygen\bin;C:\Program Files\NVIDIA Corporation\Cg\bin;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Git\cmd;C:\Program Files\TortoiseGit\bin;C:\Program Files\Notepad++;C:\Program Files\TortoiseSVN\bin;C:\Dev\Python27

      The initialisation script used for msvc2008 (as a kit in Creator) adds the correct path to PATH when run manually from the command line:

      c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE;c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN;c:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools;c:\WINDOWS\Microsoft.NET\Framework\v3.5;c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;c:\Program Files\Microsoft Visual Studio 9.0\VC\VCPackages;C:\Program Files\\Microsoft SDKs\Windows\v6.0A\bin;C:\Dev\qt-creator-windows-2.5.82-233-2012-09-11_00-02-15\bin;C:\Dev\Perl\site\bin;C:\Dev\Perl\bin;C:\Dev\MinGW\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\jEdit;C:\Program Files\doxygen\bin;C:\Program Files\NVIDIA Corporation\Cg\bin;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Git\cmd;C:\Program Files\TortoiseGit\bin;C:\Program Files\Notepad++;C:\Program Files\TortoiseSVN\bin;C:\Dev\Python27 
      

      When using the Visual Studio 2008 Command Prompt (from which I can build the same project without problems), the path is identical:

      c:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE;c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN;c:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools;c:\WINDOWS\Microsoft.NET\Framework\v3.5;c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;c:\Program Files\Microsoft Visual Studio 9.0\VC\VCPackages;C:\Program Files\\Microsoft SDKs\Windows\v6.0A\bin;C:\Dev\qt-creator-windows-2.5.82-233-2012-09-11_00-02-15\bin;C:\Dev\Perl\site\bin;C:\Dev\Perl\bin;C:\Dev\MinGW\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\jEdit;C:\Program Files\doxygen\bin;C:\Program Files\NVIDIA Corporation\Cg\bin;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Git\cmd;C:\Program Files\TortoiseGit\bin;C:\Program Files\Notepad++;C:\Program Files\TortoiseSVN\bin;C:\Dev\Python27 
      

      The output when building with nmake from the Visual Studio 2008 Command Prompt:

      	"c:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe" -f Makefile.Debug
      	cl -c -nologo -Zm200 -Zc:wchar_t -Zi -MDd -GR -W3 -w34100 -w34189 -EHsc -DUNICODE -DWIN32 -DQT_QML_DEBUG -I"..\..\qtbase-debug\mkspecs\win32-msvc2008" -Fodebug\ @C:\DOCUME~1\Mitch!\LOCALS~1\Temp\nm38CD.tmp
      main.cpp
      	echo 1 /* CREATEPROCESS_MANIFEST_RESOURCE_ID */ 24 /* RT_MANIFEST */ "debug\\cl-test.exe.embed.manifest">debug\cl-test.exe_manifest.rc
      	if not exist debug\cl-test.exe del debug\cl-test.exe.embed.manifest>NUL 2>&1
      	if exist debug\cl-test.exe.embed.manifest copy /Y debug\cl-test.exe.embed.manifest debug\cl-test.exe_manifest.bak
      	link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:CONSOLE "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /MANIFEST /MANIFESTFILE:debug\cl-test.exe.embed.manifest /OUT:debug\cl-test.exe @C:\DOCUME~1\Mitch!\LOCALS~1\Temp\nm38CE.tmp
      	if exist debug\cl-test.exe_manifest.bak fc /b debug\cl-test.exe.embed.manifest debug\cl-test.exe_manifest.bak >NUL || del debug\cl-test.exe_manifest.bak
      	if not exist debug\cl-test.exe_manifest.bak rc.exe /fodebug\cl-test.exe_manifest.res debug\cl-test.exe_manifest.rc
      Microsoft (R) Windows (R) Resource Compiler Version 6.0.5724.0
      
      Copyright (C) Microsoft Corporation.  All rights reserved.
      
      
      	if not exist debug\cl-test.exe_manifest.bak link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:CONSOLE "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /MANIFEST /MANIFESTFILE:debug\cl-test.exe.embed.manifest /OUT:debug\cl-test.exe @C:\DOCUME~1\Mitch!\LOCALS~1\Temp\nm38D0.tmp
      	if exist debug\cl-test.exe_manifest.bak del debug\cl-test.exe_manifest.bak
      

      The output when building with jom (the same .exe that Creator uses) from the Visual Studio 2008 Command Prompt:

      	C:\Dev\qt-creator-windows-2.5.82-233-2012-09-11_00-02-15\bin\jom.exe -f Makefile.Debug
      	cl -c -nologo -Zm200 -Zc:wchar_t -Zi -MDd -GR -W3 -w34100 -w34189 -EHsc -DUNICODE -DWIN32 -DQT_QML_DEBUG -I"..\..\qtbase-debug\mkspecs\win32-msvc2008" -Fodebug\ @C:\DOCUME~1\Mitch!\LOCALS~1\Temp\main.obj.3376.0.jom
      main.cpp
      	echo 1 /* CREATEPROCESS_MANIFEST_RESOURCE_ID */ 24 /* RT_MANIFEST */ "debug\\cl-test.exe.embed.manifest">debug\cl-test.exe_manifest.rc
      	if not exist debug\cl-test.exe del debug\cl-test.exe.embed.manifest>NUL 2>&1
      	if exist debug\cl-test.exe.embed.manifest copy /Y debug\cl-test.exe.embed.manifest debug\cl-test.exe_manifest.bak
      	link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:CONSOLE "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /MANIFEST /MANIFESTFILE:debug\cl-test.exe.embed.manifest /OUT:debug\cl-test.exe @C:\DOCUME~1\Mitch!\LOCALS~1\Temp\cl-test.exe.3376.1203.jom
      	if exist debug\cl-test.exe_manifest.bak fc /b debug\cl-test.exe.embed.manifest debug\cl-test.exe_manifest.bak >NUL || del debug\cl-test.exe_manifest.bak
      	if not exist debug\cl-test.exe_manifest.bak rc.exe /fodebug\cl-test.exe_manifest.res debug\cl-test.exe_manifest.rc
      Microsoft (R) Windows (R) Resource Compiler Version 6.0.5724.0
      
      Copyright (C) Microsoft Corporation.  All rights reserved.
      
      
      	if not exist debug\cl-test.exe_manifest.bak link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:CONSOLE "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /MANIFEST /MANIFESTFILE:debug\cl-test.exe.embed.manifest /OUT:debug\cl-test.exe @C:\DOCUME~1\Mitch!\LOCALS~1\Temp\cl-test.exe.3376.1219.jom
      	if exist debug\cl-test.exe_manifest.bak del debug\cl-test.exe_manifest.bak
      

      I can verify that the TMP and TEMP environment variables are writable from within Creator.

      Attachments

        1. 9ANx3.png
          9ANx3.png
          42 kB
        2. FIGpX.png
          FIGpX.png
          9 kB

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              dt Daniel Teske
              mitch_curtis Mitch Curtis
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes