cpython/Tools/buildbot/build.bat

@rem Used by the buildbot "compile" step.
cmd /c Tools\buildbot\external.bat
call "%VS71COMNTOOLS%vsvars32.bat"
cmd /q/c Tools\buildbot\kill_python.bat
devenv.com /useenv /build Debug PCbuild\pcbuild.sln
Added brief comments. 2006-03-12 02:47:36 -04:00			`@rem Used by the buildbot "compile" step.`
Update to bzip2 1.0.3 Make buildbot slaves automatically fetch bzip2 1.0.3. 2006-03-13 06:52:04 -04:00			`cmd /c Tools\buildbot\external.bat`
Add buildbot support scripts. 2006-03-05 12:18:44 -04:00			`call "%VS71COMNTOOLS%vsvars32.bat"`
Merge p3yk branch with the trunk up to revision 45595. This breaks a fair number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway. 2006-04-21 07:40:58 -03:00			`cmd /q/c Tools\buildbot\kill_python.bat`
Adding the /useenv means that one's PATH actually gets through. This is important for the _ssl.vproj build. It calls build_ssl.py which tries to find a Perl to use. Without "/useenv" Visual Studio is getting a PATH from somewhere else (presumably from its internal environment configuration). The result is that build_ssl.py fallsback to its "well-known" locations for a Perl install. 2006-03-12 19:40:58 -04:00			`devenv.com /useenv /build Debug PCbuild\pcbuild.sln`