023b9f952a
Package wininst*.exe from distutils/command.
2008-04-09 18:56:20 +00:00
775e10d9e6
Suppress compilation of py3_ files upon installation.
2008-04-08 16:48:35 +00:00
1e72feced3
Make the "private CRT" case work, by editing the
...
manifest in DLLs to refer to the root copy of the CRT.
2008-04-07 16:34:04 +00:00
46a8be7a35
Drop support for 7.1 CRT.
2008-04-07 14:55:53 +00:00
e411f8955f
Make private_crt feature object a global variable.
2008-04-07 14:54:16 +00:00
54d489a97f
Delete ALLUSERS property merged from CRT merge module, so that per-user installations become possible again.
2008-04-07 14:53:34 +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
db508be07e
Add script to merge msvcr90.
2008-04-05 15:50:58 +00:00
4dc3415def
Add two features to distinguish between private and SxS CRT.
2008-04-05 15:48:36 +00:00
5f187fba31
Extend sizes of various fields, to support the CRT90 merge module.
2008-04-05 15:45:25 +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
980c598936
Remove the building of Berkeley DB step; _bsddb44.vcproj takes care of this for us now.
2008-04-03 15:39:17 +00:00
5b63acd31e
#2503 make singletons compared with "is" not == or !=
...
Thanks to Wummel for the patch
2008-03-29 15:24:25 +00:00
cdbc977c03
Install 2to3 script.
2008-03-24 12:57:53 +00:00
27f60a65e8
Comment out tcltk/tcltk64 removal.
2008-03-19 22:41:10 +00:00
e7abf20ce7
Force a clean of the tcltk/tcltk64 directories now that we've completely changed the tcl/tk build environment.
2008-03-19 21:51:16 +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
12b580b2c6
Checkout sqlite-source when it is not there.
2008-03-19 16:10:57 +00:00
4f4738f015
Lets have another try at getting the Windows buildbots in a consistent state before rebuilding using the new process.
2008-03-19 09:23:08 +00:00
4fbaacaa12
Fix the tcl-8.4.18.1 path and make sure we cd into the right directory when building tcl/tk.
2008-03-19 08:06:03 +00:00
05a96641b4
Refine the Visual Studio 2008 build solution in order to improve how we deal with external components, as well as fixing outstanding issues with Windows x64 build support. Introduce two new .vcproj files, _bsddb44.vcproj and sqlite3.vcproj, which replace the previous pre-link event scripts for _bsddb and _sqlite3 respectively. The new project files inherit from our property files as if they were any other Python module. This has numerous benefits. First, the components get built with exactly the same compiler flags and settings as the rest of Python. Second, it makes it much easier to debug problems in the external components when they're part of the build system. Third, they'll benefit from profile guided optimisation in the release builds, just like the rest of Python core.
...
I've also introduced a slightly new pattern for managing externals in subversion. New components get checked in as <name>-<version>.x, where <version> matches the exact vendor version string. After the initial import of the external component, the .x is tagged as .0 (i.e. tcl-8.4.18.x -> tcl-8.4.18.0). Some components may not need any tweaking, whereas there are others that might (tcl/tk fall into this bucket). In that case, the relevant modifications are made to the .x branch, which will be subsequently tagged as .1 (and then n+1 going forward) when they build successfully and all tests pass. Buildbots will be converted to rely on these explicit tags only, which makes it easy for us to switch them over to a new version as and when required. (Simple change to external(-amd64).bat: if we've bumped tcl to 8.4.18.1, change the .bat to rmdir 8.4.18.0 if it exists and check out a new .1 copy.)
2008-03-19 07:45:19 +00:00
a8b09fd4c3
Add Tools/scripts/patchcheck.py. Invoked from ``make check``, the script does
...
some verification:
- Runs reindent.py on all .py files.
- Checks if any changes in Doc exist.
- Whether Misc/ACKS was changed.
- Whether Misc/NEWS was changed.
The hope is that ``make check`` can become a command anybody can run to get
reminders about what all the requisite steps needed to create a proper
patch/checkin.
2008-03-18 17:25:13 +00:00
f2b333a0c9
Run debug version, cd to PCbuild.
2008-03-14 21:19:28 +00:00
7bae4432a3
Use -x64 flag.
2008-03-14 13:57:59 +00:00
3accbb0729
Well that was dumb. platform.python_implementation returns a function, not a
...
string.
2008-03-08 21:35:15 +00:00
019e9d730a
Fix pybench for pythons < 2.6, tested back to 2.3.
2008-03-08 20:08:21 +00:00
0df0f6d1b2
Add tests for with and finally performance to pybench.
2008-03-08 18:26:54 +00:00
db311ba588
Update db-4.4.20 build procedure.
2008-03-06 13:50:28 +00:00
4291b19d4e
cd PCbuild only after deleting all pyc files.
2008-03-05 22:24:31 +00:00
0e795e7d92
Package Tcl from tcltk64 on AMD64.
2008-02-29 20:54:44 +00:00
8b6552deb3
Build db-4.4.20 with VS9; remove VS2003 build if necessary.
2008-02-29 18:17:23 +00:00
03dc56cd17
Locate VS installation dir from environment, so that it works with the express edition.
2008-02-28 22:20:50 +00:00
d9759c4880
Bundle msvcr90.dll as a "private assembly".
2008-02-28 19:57:34 +00:00
1c5105d668
Add 2.6aN uuids.
2008-02-28 19:44:22 +00:00
4219da4bd0
Issue 2117. Update compiler module to handle class decorators.
...
Thanks Thomas Herve
2008-02-25 18:06:00 +00:00
c5f05e45cf
Patch #2167 from calvin: Remove unused imports
2008-02-23 17:40:11 +00:00
f88a077f69
Now we handle different the backup copy, because of security
...
issues regarding user/group and permissions. Fixes 1050828.
2008-02-17 16:21:13 +00:00
1ea8cb49ed
#1726198 : replace while 1: fp.readline() with file iteration.
2008-01-21 17:22:06 +00:00
bd865db90c
Added win_add2path.py to Tools/scripts/
...
Added builddoc.bat to Doc/
2008-01-18 11:58:50 +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
f71b59b072
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:04 +00:00
94da1d6a21
Don't try to package msvcr90 for the moment.
2008-01-06 11:13:16 +00:00
e7a434e41b
Package using VS 2008.
2008-01-06 11:03:43 +00:00
4b3311b25b
Use vcbuild for VS 2009.
2008-01-06 10:09:48 +00:00
9fd2bcf654
Test in PCbuild directory.
2008-01-01 23:36:24 +00:00
76f1c1f304
Use Visual Studio 2009 on the build slaves.
2008-01-01 23:00:48 +00:00
e1c6af06ec
The root of the project is two levels up from PC/VS7.1
2008-01-01 13:58:16 +00:00
7e28e495a4
Added new wininst files to msi.py and adjusted some paths
2008-01-01 13:52:57 +00:00
e604eb9a35
MSI uses back slashes as path separators
2008-01-01 13:40:26 +00:00
ce49f02063
Fix paths for build bot, part 2
2007-12-31 15:02:41 +00:00
Martin v. Löwis
Trent Nelson
Benjamin Peterson
Thomas Heller
Brett Cannon
Jeffrey Yasskin
Facundo Batista
Christian Heimes
Georg Brandl