Hacker News new | ask | show | jobs
by rogerbinns 5116 days ago
If only it was so easy. The existing Python versions need VS2008 so I have to use Platform SDK 7.0 (not 7.1). Then it and VS2008 won't play nice with paths, so in the end I just hardcoded them in my setup script. http://code.google.com/p/apsw/wiki/Win7build

The next Python release is using VS2012 so I'll have to have it, whatever it takes to get it and 64 bit binaries, plus VS2008 and PSDK 7.0 all installed at the same time.

The ultimate cause of all this is Microsoft bundling the C library with the compiler, and not being able to have more than one version of the C library in a process which forces the executable and all dlls to be compiled with the same compiler version.

1 comments

Yup. For that reason I stick with the WDK 7.1 (and target MSVCRT.DLL by linking with msvcrt_win2000.obj, and this works on XP). Yes this would not work for Python built with VS2008, but it would not require me to carry MSVCRxx.DLLs everywhere.