"'cl' is not recognized as an internal or external command" error after VS2019 update?
-
wrote on 10 Dec 2020, 20:43 last edited by
Hi,
I use Qt 5.14.2 MSVC2017. I have also VS2019 Community.
I got "update warning" from VS Updater unfortunatelly I confirmed... :(After than update apply I rearrange kits in Qt Options.
And now I can not run project in Qt. Below message appear.'cl' is not recognized as an internal or external command, operable program or batch file. jom: D:\Belgeler\Qt\build-MegYonetim-Desktop_Qt_5_14_2_MSVC2017_64bit-Release\Makefile.Release [release\delegatemiktar.obj] Error 1 jom: D:\Belgeler\Qt\build-MegYonetim-Desktop_Qt_5_14_2_MSVC2017_64bit-Release\Makefile [release] Error 2 23:38:48: The process "C:\Qt\Tools\QtCreator\bin\jom.exe" exited with code 2. Error while building/deploying project MegYonetim (kit: Desktop Qt 5.14.2 MSVC2017 64bit) When executing step "Make"
Regards,
Mucip:) -
wrote on 11 Dec 2020, 07:27 last edited by
I think it is because after the update, the full path of cl.exe has changed.
Normally Qt uses vcvarsall.bat to set the enviroment, so there won't be any problem.
But when you set the Path of the project, it saved in the pro.user with the old Path. -
Hi,
I use Qt 5.14.2 MSVC2017. I have also VS2019 Community.
I got "update warning" from VS Updater unfortunatelly I confirmed... :(After than update apply I rearrange kits in Qt Options.
And now I can not run project in Qt. Below message appear.'cl' is not recognized as an internal or external command, operable program or batch file. jom: D:\Belgeler\Qt\build-MegYonetim-Desktop_Qt_5_14_2_MSVC2017_64bit-Release\Makefile.Release [release\delegatemiktar.obj] Error 1 jom: D:\Belgeler\Qt\build-MegYonetim-Desktop_Qt_5_14_2_MSVC2017_64bit-Release\Makefile [release] Error 2 23:38:48: The process "C:\Qt\Tools\QtCreator\bin\jom.exe" exited with code 2. Error while building/deploying project MegYonetim (kit: Desktop Qt 5.14.2 MSVC2017 64bit) When executing step "Make"
Regards,
Mucip:)@Mucip said in "'cl' is not recognized as an internal or external command" error after VS2019 update?:
After than update apply I rearrange kits in Qt Options
Why and in what way?
Do you now have any warnings/errors in your Kits? -
@Mucip said in "'cl' is not recognized as an internal or external command" error after VS2019 update?:
After than update apply I rearrange kits in Qt Options
Why and in what way?
Do you now have any warnings/errors in your Kits?wrote on 11 Dec 2020, 06:16 last edited by@jsulm ,
I just started Qt Cereator with hope but I got below "General Message"2020-12-11T09:12:57 Clang Code Model: Error: The clangbackend executable "C:\Qt\Tools\QtCreator\bin\clangbackend.exe" could not be started (timeout after 10000ms). Error while parsing file D:\Belgeler\Qt\MegYonetim\MegYonetim.pro. Giving up. Project ERROR: Cannot run compiler 'cl'. Output: =================== =================== Maybe you forgot to setup the environment?
And my Kits screen is like this. I've got more than one android kit and I don't know why?
Regards,
Mucip:) -
@jsulm ,
I just started Qt Cereator with hope but I got below "General Message"2020-12-11T09:12:57 Clang Code Model: Error: The clangbackend executable "C:\Qt\Tools\QtCreator\bin\clangbackend.exe" could not be started (timeout after 10000ms). Error while parsing file D:\Belgeler\Qt\MegYonetim\MegYonetim.pro. Giving up. Project ERROR: Cannot run compiler 'cl'. Output: =================== =================== Maybe you forgot to setup the environment?
And my Kits screen is like this. I've got more than one android kit and I don't know why?
Regards,
Mucip:)@Mucip Did you try a complete/clean rebuild: delete build folder, run qmake, build?
-
wrote on 11 Dec 2020, 06:23 last edited by
@jsulm ,
Yes.
I deleted compiled folder. Run qmake and build again. Unfortunatelly same error.Error while parsing file D:\Belgeler\Qt\MegYonetim\MegYonetim.pro. Giving up. Project ERROR: Cannot run compiler 'cl'. Output: =================== =================== Maybe you forgot to setup the environment?
Regards,
Mucip:) -
wrote on 11 Dec 2020, 06:26 last edited by
Go to "Compilers" and click Re-detect, then Apply.
-
wrote on 11 Dec 2020, 06:41 last edited by
If you start command prompt from "x64 Native Tools Command Prompt for VS 2019" in the start menu, can you run cl?
-
If you start command prompt from "x64 Native Tools Command Prompt for VS 2019" in the start menu, can you run cl?
-
wrote on 11 Dec 2020, 06:55 last edited by
Hmm...I'm out of ideas, had you change the Path in your project's Build Environment?
-
@Bonnie ,
Yes, I added PostgreSQL driver paths only.But everythig wa OK before then VS2019 update.:(
Regards,
Mucip:) -
wrote on 11 Dec 2020, 07:18 last edited by
@Bonnie
I think I found a solution with your helps.I deleted pro.user file in the project directory and recreated with Qt Creator.
I added PostgreSQL ODBC paths in Build Environment path.Than all is fine now.
But I don't know why it is happened like this?!
Thank you all guys. :)
Regards,
Mucip:) -
wrote on 11 Dec 2020, 07:27 last edited by
I think it is because after the update, the full path of cl.exe has changed.
Normally Qt uses vcvarsall.bat to set the enviroment, so there won't be any problem.
But when you set the Path of the project, it saved in the pro.user with the old Path. -
I think it is because after the update, the full path of cl.exe has changed.
Normally Qt uses vcvarsall.bat to set the enviroment, so there won't be any problem.
But when you set the Path of the project, it saved in the pro.user with the old Path.
1/15