Commit Graph

11 Commits

Author SHA1 Message Date
Trent Nelson 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
Trent Nelson 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
Trent Nelson 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
Trent Nelson 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
Martin v. Löwis db311ba588 Update db-4.4.20 build procedure. 2008-03-06 13:50:28 +00:00
Thomas Heller 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
Thomas Heller 22000cbd6b Build bzip2. 2007-06-13 07:54:57 +00:00
Thomas Heller 92094d0f1c Do not hardcode the buildbot's directory name. 2007-06-13 07:07:03 +00:00
Thomas Heller de15cdf995 Don't rebuild Berkeley DB if not needed (this was committed by accident). 2007-06-12 19:56:12 +00:00
Thomas Heller 285216ca30 Add bufferoverflowU.lib to PCBuild\_bsddb.vcproj.
Build sqlite3.dll and bsddb.
2007-06-12 19:02:59 +00:00
Thomas Heller 04d17b4660 Checkout, but do not yet try to build, exernal sources. 2007-06-12 15:36:22 +00:00