[Qt-creator] Toolchain detection Windows SDK amd64

Peter Kümmel syntheticpp at gmx.net
Tue Nov 20 11:40:55 CET 2012

On 20.11.2012 00:21, Wolfgang Baron wrote:
> Hi,
> Peter Kümmel wrote:
>> /amd64 and /x86 are the same, have a look at vcvarsall.bat:
>> if /i %1 == amd64     goto amd64
>> if /i %1 == x64       goto amd64
>> I assume your real problem is different.
> No. The fix would not work then, right? In your answer, you are
> referring to vcvarsall.bat, which is used for the compiler called
> "Microsoft Visual C++ Compiler 10.0 (amd64)". I am talking about the
> Windows SDK version called "Microsoft Windows SDK for Windows 7
> (7.1.7600.0.30514) (amd64)", as quoted in my fixed entry for toolchains.xml:
>    <valuemap type="QVariantMap">
>     <value type="QString"
> key="ProjectExplorer.MsvcToolChain.SupportedAbi">x86-windows-msvc2010-pe-64bit</value>
>     <value type="QString"
> key="ProjectExplorer.MsvcToolChain.VarsBat">C:/Program Files/Microsoft
> SDKs/Windows/v7.1/bin/SetEnv.cmd</value>
>     <value type="QString"
> key="ProjectExplorer.MsvcToolChain.VarsBatArg">/x64</value>
>     <value type="bool"
> key="ProjectExplorer.ToolChain.Autodetect">false</value>
>     <value type="QString"
> key="ProjectExplorer.ToolChain.DisplayName">Windows SDK 7.1 x64</value>
>     <value type="QString"
> key="ProjectExplorer.ToolChain.Id">ProjectExplorer.ToolChain.Msvc:{7afba206-0e0e-4e07-a623-2932c01e21f4}</value>
>    </valuemap>
> The Windows SDK version of the compiler uses setenv.cmd, which only
> knows about x64, not amd64.

Does your compiler dialog also list "Microsoft Visual C++ Compiler 10.0 (amd64)?
Then you could use this compiler (or x86_amd64 when you are on a 32bit Windows).
setenv.cmd only maps to these compilers.
Maybe the Windows SDK entries for the compilers are superfluously. Could you check
how many cl.exe versions are on your system?

> I proposed a workaround for a bug in the autodetection. I browsed a
> little in the buglists, but did not find an exact match. Before I open a
> new Bug, I wanted to know, whether this applies to a bug, which has
> already been published. Anyone?

If you can't find a existing report file a new one. There will be some cleanup in 2.7.

I've fixed the autodetection code, could you check if this version works:


More information about the Qt-creator mailing list