611c86b7d1
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 21:11:55 +00:00
76f1c1f304
Use Visual Studio 2009 on the build slaves.
2008-01-01 23:00:48 +00:00
656dc2adee
Fix paths for build bot
2007-12-31 14:59:26 +00:00
70f5f7a9f4
Use GetModuleFileNameEx instead of GetProcessImageFileName,
...
as the latter is not available on Windows 2000.
2006-04-17 17:26:42 +00:00
ce8607df96
Revert to 45478, disable kill_python command for now.
2006-04-17 10:39:39 +00:00
63d1f99d7a
Rename binary again; increase noise; stop trying to actually kill the process.
2006-04-17 10:31:35 +00:00
2d12372e32
Add kill_python command.
2006-04-17 09:46:47 +00:00
14c1cf88ad
Update to bzip2 1.0.3
...
Make buildbot slaves automatically fetch bzip2 1.0.3.
2006-03-13 10:52:04 +00:00
b1386772b5
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 23:40:58 +00:00
d39ab5bf97
Move buildbot scripts to Tools/buildbot.
2006-03-12 09:50:39 +00:00
Trent Nelson
Martin v. Löwis
Christian Heimes
Trent Mick