Thanks for letting me know about this. I installed Subversion and tried to make the build work like that, but it fails.
1) I am building 64-bit on Vista, so I used build-amd64.bat instead of build.bat. 2) build-amd64.bat was setup to use MSVS 9.0, while I am using MSVS 8.0. Also, some of the BATCH programs incorrectly added a backslash after the %VS90COMNTOOLS% environment variable. I corrected those to use %VS80COMNTOOLS%, without the backslash. 3) It then complained about incompatible solution/project files, so I modified build-amd64.bat to use the solution/project files in pc\vs8.0 instead of pcbuild. 4) It now has errors/warnings like: C:\Program Files (x86)\Microsoft Visual Studio 8\VC\PlatformSDK\include \prsht.h(531) : error C2016: C requires that a struct or union has at least one member ... c1 : fatal error C1083: Cannot open source file: '..\..\.. \db-4.4.20\common\zerofill.c': No such file or directory xa_map.c ... 4>..\..\Python\getargs.c(319) : warning C4244: 'function' : conversion from 'Py_ssize_t' to 'int', possible loss of data So I don't see how the amd64-bit builds are working out of the box on MS Windows Vista, and I may have made some error when changing the build files. I'd appreciate any other thoughts ... Bev in TX On Jul 20, 10:36 am, Tim Golden <[EMAIL PROTECTED]> wrote: > I'll leave others to comment on whether or not > it's expected to build with VS2005, but the easiest > way to get a debug build is to pretend to be a buildbot. > > 1) Check out the python source into, say, c:\dev\python > > svn cohttp://svn.python.org/projects/python/trunkc:\dev\python > > 2) Switch to that directory > > cd \dev\python > > 3) Pretend to be a buildbot > > tools\buildbot\build > > This will checkout all the necessary sources into, in my > example, c:\dev. It will then run all the build steps > necessary to get a debug build which will then be in > > c:\dev\python\pcbuild\python_d.exe > > TJG -- http://mail.python.org/mailman/listinfo/python-list
