Does QT actually call VCVARSALL.BAT?
-
Very strange. I don't know what's going on, but this user seems to have found a way around the issue: http://qt-project.org/forums/viewreply/163521/
-
Dear JKSH!
Yes , this is workaround but this is not solution. Imagine that I can have both 2010 and 2012 studio (actually it is so). In that case I have to restart the qt creator switching between 2010 and 2012.
Remark that this applies to express versions. On my work machine (windows 7 pro + visual studio 2010 pro + qt 5.2.1) there is no such problem.
-
If you're willing, please post a bug report at https://bugreports.qt-project.org/ and attach your screenshots.
This might help the Qt Creator team find a proper solution.
I don't think the problem is with Express -- I use MSVC 2012 and MSVC 2013 Express with Qt Creator, with no issues.
-
I have reported here https://bugreports.qt-project.org/browse/QTCREATORBUG-11539
Thank you for your time JKSH!
-
[quote author="JKSH" date="1393035362"]
I don't think the problem is with Express -- I use MSVC 2012 and MSVC 2013 Express with Qt Creator, with no issues.[/quote]I found one moment that may became cause of the problem. This is profile name. On my work machine I have latin profile name
APPDATA=C:\Users\Stranger\AppData\Roaming, but on home machine there is cyrillic profile name:
APPDATA=C:\Users\Толик\AppData\Roaming -
Great; thank you for your report! I hope it can help fix this issue.
-
Hi :) Found this post while searching for "'cl' is not recognized as an internal or external command". I got this message in Qt Creator building a project with Qt 4.8.5 and MSVC 2010. Strange thing since it worked earlier today.
I found the reason and solution for me: an application I had installed in the mean time (between working and non working compiling in Creator) had wiped out my System PATH variable. Luckily I was able to recover it using this post on SuperUser: http://superuser.com/a/265575
Might not be relevant for the original posters problem, but others may end up here like me searching for the same problem. :)
-
Daniel Teske has found workaround: https://bugreports.qt-project.org/browse/QTCREATORBUG-11539
You should redirect TMP to path without non-latin non-space characters. For example TMP=c:\tmp works fine.
-
Hey. This topic ranks high in Google searches for similar problem, so I'm adding that users of Qt 5.7.0 / MSVC2015 might hit what looks like a QTCreator bug, where QTCreator incorrectly runs VC's initialization script. See QTCREATORBUG-16397 - MSVC2015 builds fail due to calling architecture-specific vcvars with architecture parameter.
-
I have experienced same thing. All environment variables related with VC was not set automatically when QtCreator launched. I solved the issue by changing Windows account name. If the account name has some special characters(like "&"), it seems the environment values are not parsed properly during invoking vcvar.
-
I have experienced same thing. All environment variables related with VC was not set automatically when QtCreator launched. I solved the issue by changing Windows account name. If the account name has some special characters(like "&"), it seems the environment values are not parsed properly during invoking vcvar.
@DY-Kim I would avoid using such user names as user names are part of paths like c:\users\USER_NAME
If a user name contains characters which have special meaning for the CMD/shell then you can expect troubles like what you described.
