cpython/Tools/buildbot/build.bat

@rem Used by the buildbot "compile" step.
cmd /c Tools\buildbot\external.bat
call "%VS90COMNTOOLS%vsvars32.bat"
cmd /q/c Tools\buildbot\kill_python.bat
cmd /c Tools\buildbot\clean.bat
vcbuild /useenv PCbuild\pcbuild.sln "Debug|Win32"
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`
Use Visual Studio 2009 on the build slaves. 2008-01-01 19:00:48 -04:00			`call "%VS90COMNTOOLS%vsvars32.bat"`
Use GetModuleFileNameEx instead of GetProcessImageFileName, as the latter is not available on Windows 2000. 2006-04-17 14:26:42 -03:00			`cmd /q/c Tools\buildbot\kill_python.bat`
Fix the x64 Windows build environment used by the buildbots. %VS90COMNTOOLS%\vsvars32.bat is fine for 32-bit builds, but doesn't work for x64 builds, regardless of /MACHINE:AMD64 and /USECL:MS_OPTERON flags passed to cl.exe. Launch the x86_64 cross compilation environment via '%VS90COMNTOOLS%\..\..\VC\vcvarsall.bat x86_amd64'. I don't have access to any systems without Visual Studio 2008 Professional installed (i.e. just Express Edition), so I can't test if x64 compilation works w/ VS Express at the moment. Additionally, force a clean in our build.bat files before building, just whilst we're going through these build system updates. And finally, add in the missing MACHINE=AMD64 option to our Tcl/Tk x64 build. 2008-03-19 18:11:55 -03:00			`cmd /c Tools\buildbot\clean.bat`
Use Visual Studio 2009 on the build slaves. 2008-01-01 19:00:48 -04:00			`vcbuild /useenv PCbuild\pcbuild.sln "Debug\|Win32"`