"'cl' is not recognized as an internal or external command" error after VS2019 update?

[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:)

[jsulm]

@Mucip Did you try a complete/clean rebuild: delete build folder, run qmake, build?

[Mucip]

@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:)

[Bonnie]

Go to "Compilers" and click Re-detect, then Apply.

[Mucip]

@Bonnie ,
I did it many times. :(
Same problem.

Regards,
Mucip:)

[Bonnie]

If you start command prompt from "x64 Native Tools Command Prompt for VS 2019" in the start menu, can you run cl?

[Mucip]

@Bonnie
Looks lik OK.

Regards,
Mucip:)

[Bonnie]

Hmm...I'm out of ideas, had you change the Path in your project's Build Environment?

[Mucip]

@Bonnie ,
Yes, I added PostgreSQL driver paths only.

But everythig wa OK before then VS2019 update.:(

Regards,
Mucip:)

[Bonnie]

@Mucip Then try to reset the Path first, and add your driver paths back after that.

[Mucip]

@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:)

[Bonnie]

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.

[Mucip]

@Bonnie
You may be right.
But I use like this more than 1 year and I made many VS2019 update in this period.
This was the first time. Interesting?!...

Regards,
Mucip:)