On 24 September 2014 07:14, <mar...@v.loewis.de> wrote: > Zitat von Paul Moore <p.f.mo...@gmail.com>: > >> Can anyone give me some advice, please? I am trying to build >> extensions on Windows 64-bit, using the free Windows SDK compilers. > > Can you please be more specific? What SDK, and what free compilers? > The bug report is about VS Express, not the SDK compilers.
For Python 2.7, I was using the "Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1" x64 version. I set DISTUTILS_USE_SDK, and got exactly the symptom mentioned in the bug. Hence my comment that I was hitting "the same" issue with a different environment. I don't know whether it is relevant, but Visual Studio 2008 Express was also installed in the environment. >> Two questions, really: >> >> * Is there any intention that building extensions with the SDK >> compilers is supported? > > As long as the SDK does include compilers: yes. > >> * How do I do it, if so? > > Open a command window with the SDK environment variables set, > then also set DISTUTILS_USE_SDK, and invoke setup.py I'm scripting the build, which means I can't use the "Open SDK command line environment" start menu item. But what I do is SetEnv.cmd /x64 /release SET DISTUTILS_USE_SDK=1 SET MSSdk=1 I then run setup.py and get the error ValueError: [u'path'] I have not yet been able to successfully set up the SDK environment locally (the above was done on a remote machine hosted by appveyor.com) but am close to doing so. My normal build machine includes the full Visual Studio (via the MSDN access you mentioned). Once I have that environment I'll be in a position to reproduce the error on my local machine and do further testing much more conveniently. Paul _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
