![syntra small run compiler syntra small run compiler](https://www.burningimage.net/cattrack/wp-content/uploads/2017/12/xc8-free-mode-1-768x330.png)
Note that vcvars64 or vcvars32 both make a reg query call for VS140COMNTOOLS. It simply sets the saved environment and skips all the reg query calls. This is updated 1x day and the result is that I can open in Qt and have a working environment. bat file that simply sets the environment variables with the determined values. The solution I arrived at is to cache the resulting environment in another. Observed Qt creating temp bat files to call vcvarsall.bat over and over and over again. Seems Qt times out when calling vcvarsall. The antivirus client was tripping up over all the reg query calls in some of the bat files and delaying things sufficiently such that Qt got an incomplete environment. Either that or there was a lingering bath path around used by MySQL which no longer existed and was throwing the toolchain.Įither way, I'm back in business! Thanks for all the comments and help with this.
#SYNTRA SMALL RUN COMPILER CODE#
All I can think of is that when the vcvarsall.bat returns an exit code, it was not the exit code expected by Qt Creator due to the MySQL issues. I then ran Qt Creator again using a simple example application and now everything works perfectly. When I executed the vcvarsall.bat file from within the Visual Studio / VC directory, I noticed that a couple of issues were being reported in the command line - notably that MySQL command not found which I thought rather odd - what would MySQL have to do with a Visual Studio install?Īnyhoo, having then removed anything and everything MySQL-related from my system, running the vcvarsall.bat again yielded no reported issues. It almost had me beat but after a little bit more digging, I've finally managed to sort it. When I re-installed Qt Creator, the same problems arose. It got to the point where I uninstalled Qt AND Visual Studio then re-installed both just to see what would happen. (Just some Thanks for your reply and thanks for the extra information. My guess is that there was some restructuring done around the MSVC make specs in recent Qt versions, and maybe in other MSVC-build-related areas, which is somehow related to your issue. In the end, it was not important for me to use the absolute latest version (Qt 5.9.1), and instead I worked around the problem by just using Qt 5.6.2 instead, which has a folder structure similar to Qt 5.5.1 (what our make system was built around). Maybe you forgot to setup the environment?". I attempted to do some copying/pasting/renaming of folders in order to get our existing make system to build with Qt 5.9.1 (without editing our make system, for reasons I won't get into), but was not successful - the build got farther, past the "Could not find qmake configuration file win32-msvc2015" error I had been seeing, but hit an error similar to what you are seeing: "Project ERROR: Cannot run compiler 'cl'. I attempted to use the latest Qt 5.9.1, and our make system failed because the Qt "mkspecs" folder in Qt 5.9.1 now contains a single "win32-msvc" folder, instead of separate "win32-msvc2005", "win32-msvc2008", "win32-msvc2010", "win32-msvc2012", "win32-msvc2013", and "win32-msvc2015" folders as it did in Qt 5.5.1. This make system was built around Qt 5.5.1, and uses the "win32-msvc2015" make spec (e.g. I just encountered a very similar problem - we have a command line build and somewhat-complex make system here which calls qmake, etc. I don't have an exact solution for you, but maybe some helpful information: I'm not really sure what has happened as it was working great with Qt 5.7.0 prior to the updates. When I check the Qt Kits, all kits have a yellow exclamation mark next to them reporting the following warnings:ĬMake configuration has no path to a C compiler set, even though the kit has a valid toolchainĬMake configuration has no path to a C++ compiler set, even though the kit has a valid toolchainĪll 32bit kits have the Microsoft Visual C++ Compiler 14.0 (x86) C/C++ compilers set and the 64bit ones have the Microsoft Visual C++ Compiler 14.0 (x86_amd64) C/C++ compilers set. If I bring up the Developer Command Prompt for VS2015, I can see that cl is clearly recognized as a tool. Maybe you forgot to setup the environment? Now, when I try to build a project within Qt Creator, it fails almost immediately with the following error:Ĭannot run compiler 'cl'. I've previously had Qt 5.7.0 installed and working a treat, using the MSVC 2015 x86 and 圆4 compilers.
#SYNTRA SMALL RUN COMPILER UPDATE#
I've recently updated my Qt to include version 5.9.1 as well as update Qt Creator to 4.3.1.