[issue24508] Backport 3.5's Windows build project files to 2.7

2015-07-15 Thread Roundup Robot
Roundup Robot added the comment: New changeset ca78b9449e04 by Zachary Ware in branch '2.7': Close #24508: Backport the 3.5 MSBuild project files. https://hg.python.org/cpython/rev/ca78b9449e04 -- nosy: +python-dev resolution: - fixed stage: patch review - resolved status: open -

[issue24508] Backport 3.5's Windows build project files to 2.7

2015-07-01 Thread Zachary Ware
Zachary Ware added the comment: Thanks for testing this, Steve! It sounds like PCbuild/readme.txt will need a significant update in the setup portion to cover the different ways to get what is needed (and to mention PC/VS9.0 as a simpler setup). I use third-party extension modules rarely

[issue24508] Backport 3.5's Windows build project files to 2.7

2015-06-27 Thread Steve Dower
Steve Dower added the comment: 32-bit build was fine (VS 2013 + SDK 7.1 + VS 2008), but something has gone funny with the 64-bit. Need to go AFK for a bit now, but I'll try and figure that out later today. -- ___ Python tracker

[issue24508] Backport 3.5's Windows build project files to 2.7

2015-06-27 Thread Steve Dower
Steve Dower added the comment: Looks like the required install configuration is: * VS 2008 + VS 2010, or * VS 2008 + VS 2013 or later + Windows SDK 7.1 The SDK is at http://www.microsoft.com/en-us/download/details.aspx?id=8279 and contains MSVC10 and platform toolset files for both VC9 and

[issue24508] Backport 3.5's Windows build project files to 2.7

2015-06-27 Thread Steve Dower
Steve Dower added the comment: 64-bit build didn't work (couldn't find ws2_32.lib) until I ran the SDK Configuration utility and selected v6.0A as the default SDK. This may be because I forgot to explicitly select the 64-bit compilers when I initially installed VS 2008, but it's a worthwhile

[issue24508] Backport 3.5's Windows build project files to 2.7

2015-06-25 Thread Steve Dower
Steve Dower added the comment: I'll try out the changes when I get a bit of time today or tomorrow and decide then what I'll do. msi.py doesn't actually build the projects AFAIK, so it's probably okay. It might try to read them to get paths though. --

[issue24508] Backport 3.5's Windows build project files to 2.7

2015-06-24 Thread Steve Dower
Steve Dower added the comment: Feel free to fix up msi.py as much as it needs. I don't particularly understand it - I just run it :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24508

[issue24508] Backport 3.5's Windows build project files to 2.7

2015-06-24 Thread Zachary Ware
Zachary Ware added the comment: Do you plan to use the old project files or the new? For the new, there should be no change in Tools/msi, which would make fixing it very easy for me ;) -- ___ Python tracker rep...@bugs.python.org

[issue24508] Backport 3.5's Windows build project files to 2.7

2015-06-24 Thread Zachary Ware
New submission from Zachary Ware: Here's the (enormous) patch backporting 3.5's project files to 2.7. It also takes care of adjusting the old project files to their new home in PC/VS9.0, and makes a couple of small adjustments in distutils.command.build_ext, FixTk, regrtest, and the Tcl/Tk