b6d633ce33
Backed out changeset: e7065fc4a6c2
2016-03-08 13:09:32 -08:00
2f7570f094
Force clean externals on buildbots.
2016-03-08 12:51:59 -08:00
4734372aa0
Close #24508 : Backport the 3.5 MSBuild project files.
...
The old project files move to PC/VS9.0 and remain supported.
VS2008 is still required to build 2.7; VS2010 (or later, plus Windows SDK 7.1)
is *also* required to use the new project files.
2015-07-16 00:24:48 -05:00
e1076aa4e2
Clean up/refactor the batch scripts used for building on Windows.
...
This is mostly a backport of issue #21907 , but also includes a few
extras necessary to make the bulidbot scripts as thin as possible.
2015-06-09 15:21:39 -05:00
b9298a4fbb
Issue #17202 : Add .bat to .hgeol to force them to CRLF.
...
Using LF can a script to fail if it tries to use a label that is
split across 512 byte blocks. Who knows why.
2015-04-13 11:54:11 -05:00
faa9ad2a46
Add updated .hgeol file and fix newlines in the 2.7 branch.
2011-03-05 15:06:13 +01:00
945c632dff
Set eol-style to CRLF for all batch files.
2008-06-14 11:51:54 +00:00
5a4d66824a
Don't run kill_python as part of the build process. Change the buildbots so they have to call it explicitly instead.
2008-04-06 20:51:23 +00:00
d6dffbcc28
Reimplement kill_python. The existing version had a number of flaws, namely, it didn't work for x64 and it wasn't precise about which python_d.exe it was killing -- it just killed the first one it came across that happened to have 'pcbuild\python_d.exe' or 'build\python_d.exe' in it's path. The new version has been rewritten from the ground up and now lives in PCbuild, instead of Tools\buildbot, and it has also been incorporated into the Visual Studio solution (pcbuild.sln) as 'kill_python'. The solution has also been altered such that kill_python is called where necessary in the build process in order to prevent any linking errors due to open file locks. In lieu of this, all of the existing bits and pieces in Tools\buildbot that called out to kill_python at various points have also been removed as they are now obsolete. Tested on both Win32 and x64.
...
Change set (included to improve usefulness of svnmerge log entry):
M PCbuild\pythoncore.vcproj
M PCbuild\pcbuild.sln
M PCbuild\release.vsprops
A PCbuild\kill_python.vcproj
M PCbuild\debug.vsprops
A PCbuild\kill_python.c
D Tools\buildbot\kill_python.bat
D Tools\buildbot\kill_python.mak
M Tools\buildbot\build.bat
D Tools\buildbot\Makefile
M Tools\buildbot\build-amd64.bat
M Tools\buildbot\buildmsi.bat
D Tools\buildbot\kill_python.c
2008-04-03 18:27:06 +00:00
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
Steve Dower
Zachary Ware
Georg Brandl
Martin v. Löwis
Trent Nelson
Christian Heimes
Trent Mick