Update PCbuild/readme.txt

It now recommends PCbuild/get_externals.bat instead of the scripts in
Tools/buildbot.

diff --git a/PCbuild/readme.txt b/PCbuild/readme.txt
index 71fb0212d8c8f4c3df7c876985221f15837fc3d5..c078d42c251c0c9dcf86ab08e44bd00b76f0dccd 100644 (file)
--- a/PCbuild/readme.txt
+++ b/PCbuild/readme.txt
@@ -123,7 +123,7 @@ bz2
 \r
     svn export http://svn.python.org/projects/external/bzip2-1.0.6\r
 \r
-    ** NOTE: if you use the Tools\buildbot\external(-amd64).bat approach for\r
+    ** NOTE: if you use the PCbuild\get_externals.bat approach for\r
     obtaining external sources then you don't need to manually get the source\r
     above via subversion. **\r
 \r
@@ -134,12 +134,12 @@ _ssl
 \r
     svn export http://svn.python.org/projects/external/openssl-1.0.2a\r
 \r
-    ** NOTE: if you use the Tools\buildbot\external(-amd64).bat approach for\r
+    ** NOTE: if you use the PCbuild\get_externals.bat approach for\r
     obtaining external sources then you don't need to manually get the source\r
     above via subversion. **\r
 \r
     The NASM assembler is required to build OpenSSL.  If you use the\r
-    Tools\buildbot\external(-amd64).bat method for getting sources, it also\r
+    PCbuild\get_externals.bat script to get external library sources, it also\r
     downloads a version of NASM, which the ssl build script will add to PATH.\r
     Otherwise, you can download the NASM installer from\r
         http://www.nasm.us/\r
@@ -174,36 +174,13 @@ _ssl
 \r
 The subprojects above wrap external projects Python doesn't control, and as\r
 such, a little more work is required in order to download the relevant source\r
-files for each project before they can be built.  The buildbots do this each\r
-time they're built, so the easiest approach is to run either external.bat or\r
-external-amd64.bat in the ..\Tools\buildbot directory from ..\, i.e.:\r
-\r
-    C:\..\svn.python.org\projects\python\trunk\PCbuild>cd ..\r
-    C:\..\svn.python.org\projects\python\trunk>Tools\buildbot\external.bat\r
-\r
-This extracts all the external subprojects from http://svn.python.org/external\r
-via Subversion (so you'll need an svn.exe on your PATH) and places them in\r
-..\externals (relative to this directory).  The external(-amd64).bat scripts\r
-will also build a debug build of Tcl/Tk; there aren't any equivalent batch files\r
-for building release versions of Tcl/Tk lying around in the Tools\buildbot\r
-directory.  If you need to build a release version of Tcl/Tk it isn't hard\r
-though, take a look at the relevant external(-amd64).bat file and find the\r
-two nmake lines, then call each one without the 'DEBUG=1' parameter, i.e.:\r
-\r
-The external-amd64.bat file contains this for tcl:\r
-    nmake -f makefile.vc COMPILERFLAGS=-DWINVER=0x0500 DEBUG=1 MACHINE=AMD64 INSTALLDIR=..\..\tcltk64 clean all install\r
-\r
-So for a release build, you'd call it as:\r
-    nmake -f makefile.vc COMPILERFLAGS=-DWINVER=0x0500 MACHINE=AMD64 INSTALLDIR=..\..\tcltk64 clean all install\r
-\r
-    XXX Should we compile with OPTS=threads?\r
-    XXX Our installer copies a lot of stuff out of the Tcl/Tk install\r
-    XXX directory.  Is all of that really needed for Python use of Tcl/Tk?\r
-\r
-This will be cleaned up in the future; ideally Tcl/Tk will be brought into our\r
-pcbuild.sln as custom .vcproj files, just as we've recently done with the\r
-_bsddb.vcproj and sqlite3.vcproj files, which will remove the need for\r
-Tcl/Tk to be built separately via a batch file.\r
+files for each project before they can be built.  The easiest way to do this\r
+is to use the `build.bat` script in this directory to build Python, and pass\r
+the '-e' switch to tell it to use get_externals.bat to fetch external sources\r
+and build Tcl/Tk and Tix.  To use get_externals.bat, you'll need to have\r
+Subversion installed and svn.exe on your PATH.  The script will fetch external\r
+library sources from http://svn.python.org/external and place them in\r
+..\externals (relative to this directory).\r
 \r
 Building for Itanium\r
 --------------------\r