Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity
cpython/Tools/buildbot/external-amd64.bat

18 lines
640 B
Batchfile
Raw Normal View History

Checkout, but do not yet try to build, exernal sources.
2007-06-12 12:36:22 -03:00
@rem Fetches (and builds if necessary) external dependencies
@rem Assume we start inside the Python source directory
Lets have another try at getting the Windows buildbots in a consistent state before rebuilding using the new process.
2008-03-19 06:23:08 -03:00
call "Tools\buildbot\external-common.bat"
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 18:11:55 -03:00
call "%VS90COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
Checkout, but do not yet try to build, exernal sources.
2007-06-12 12:36:22 -03:00
Lets have another try at getting the Windows buildbots in a consistent state before rebuilding using the new process.
2008-03-19 06:23:08 -03:00
if not exist tcltk64\bin\tcl84g.dll (
cd tcl-8.4.18.2\win
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 18:11:55 -03:00
nmake -f makefile.vc COMPILERFLAGS=-DWINVER=0x0500 DEBUG=1 MACHINE=AMD64 INSTALLDIR=..\..\tcltk64 clean all install
Lets have another try at getting the Windows buildbots in a consistent state before rebuilding using the new process.
2008-03-19 06:23:08 -03:00
cd ..\..
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 17:35:04 -04:00
)
Checkout, but do not yet try to build, exernal sources.
2007-06-12 12:36:22 -03:00
Lets have another try at getting the Windows buildbots in a consistent state before rebuilding using the new process.
2008-03-19 06:23:08 -03:00
if not exist tcltk64\bin\tk84g.dll (
cd tk-8.4.18.1\win
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 18:11:55 -03:00
nmake -f makefile.vc COMPILERFLAGS=-DWINVER=0x0500 DEBUG=1 MACHINE=AMD64 INSTALLDIR=..\..\tcltk64 TCLDIR=..\..\tcl-8.4.18.2 clean all install
Lets have another try at getting the Windows buildbots in a consistent state before rebuilding using the new process.
2008-03-19 06:23:08 -03:00
cd ..\..
Checkout, but do not yet try to build, exernal sources.
2007-06-12 12:36:22 -03:00
)