tag:help.appveyor.com,2012-11-13:/discussions/kb/6-failing-to-set-up-environment-for-64-bit-compilers-from-sdk-v70AppVeyor: Discussion 2018-08-25T01:48:12Ztag:help.appveyor.com,2012-11-13:Comment/346781752014-09-22T23:50:15Z2014-09-22T23:50:15ZFailing to set up environment for 64-bit compilers from SDK v7.0<div><p>I don't know what's the problem with a script for SDK 7.0, but
the one for SDK 7.1 works:</p>
<pre>
<code>"C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /x64</code>
</pre></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/346781752014-09-23T08:20:24Z2014-09-23T08:20:24ZFailing to set up environment for 64-bit compilers from SDK v7.0<div><p>Yes, it's odd. Unfortunately, to build artifacts for Python 2.7,
I need to use the v7.0 SDK. I'll install the two SDKs locally and
see if I can see why they are behaving differently.</p></div>p.f.mooretag:help.appveyor.com,2012-11-13:Comment/346781752014-09-23T12:22:21Z2014-09-23T12:22:21ZFailing to set up environment for 64-bit compilers from SDK v7.0<div><p>I've just checked this on a local SDK v7.0 install, and I get
the same error. Looks like it's a microsoft bug :-(</p></div>p.f.mooretag:help.appveyor.com,2012-11-13:Comment/346781752014-09-24T01:45:42Z2014-09-24T01:45:42ZFailing to set up environment for 64-bit compilers from SDK v7.0<div><p>Maybe it could be fixed somehow, for example changing
<code>Cmd</code> to <code>cmd</code>?..</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/346781752014-09-24T06:32:16Z2014-09-24T06:32:16ZFailing to set up environment for 64-bit compilers from SDK v7.0<div><p>It seems like running the script via a batch file that includes
"setlocal<br>
enabledelayedexpansion" fixes the issue.</p></div>p.f.mooretag:help.appveyor.com,2012-11-13:Comment/346781752014-09-24T06:35:20Z2014-09-24T06:35:20ZFailing to set up environment for 64-bit compilers from SDK v7.0<div><p>Great finding, thanks! This is worth moving to KB area.</p></div>Feodor Fitsner