0e4497a32b
Deprecate unused scripts in Tools/buildbot.
...
I would just outright delete them, but the readme in PCbuild recommended
their use, so I figure it would be nice to leave them there for a while.
2015-06-16 10:56:14 -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
a14a06fe0e
Issue #15170 : Quote the variable that expands to the current directory.
2012-06-30 18:46:02 +02:00
ea1eda2a29
Issue #15170 : Try the HOST_PYTHON hack for 2.7.
2012-06-25 15:20:51 +02: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
61390fd884
Change amd64 buildbot scripts to use Visual Studio 2008, and
...
to use the required versions of external sources.
External sources are not yet built, so the build-step fails to
built some targets.
2008-01-09 21:35:43 +00:00
656dc2adee
Fix paths for build bot
2007-12-31 14:59:26 +00:00
04d17b4660
Checkout, but do not yet try to build, exernal sources.
2007-06-12 15:36:22 +00:00
3608a163a6
First version of build scripts for Windows/AMD64 (no external
...
components are built yet, and 'kill_python' is disabled).
2007-06-10 15:59:17 +00:00
Zachary Ware
Stefan Krah
Georg Brandl
Martin v. Löwis
Trent Nelson
Thomas Heller
Christian Heimes