|
182 | 182 | to be somewhere on your PATH. More recent versions of OpenSSL may |
183 | 183 | need a later version of NASM. If OpenSSL's self tests don't pass, |
184 | 184 | you should first try to update NASM and do a full rebuild of |
185 | | - OpenSSL. If you use the Tools\buildbot\external(-amd64).bat method |
| 185 | + OpenSSL. If you use the PCbuild\get_externals.bat method |
186 | 186 | for getting sources, it also downloads a version of NASM which the |
187 | 187 | ssl build script will add to PATH. |
188 | 188 |
|
@@ -236,45 +236,13 @@ Getting External Sources |
236 | 236 | The last category of sub-projects listed above wrap external projects |
237 | 237 | Python doesn't control, and as such a little more work is required in |
238 | 238 | order to download the relevant source files for each project before they |
239 | | -can be built. The buildbots must ensure that all libraries are present |
240 | | -before building, so the easiest approach is to run either external.bat |
241 | | -or external-amd64.bat (depending on platform) in the ..\Tools\buildbot |
242 | | -directory from ..\, i.e.: |
243 | | - |
244 | | - C:\python\cpython\PCbuild>cd .. |
245 | | - C:\python\cpython>Tools\buildbot\external.bat |
246 | | - |
247 | | -This extracts all the external sub-projects from |
248 | | - http://svn.python.org/projects/external |
249 | | -via Subversion (so you'll need an svn.exe on your PATH) and places them |
250 | | -in ..\externals (relative to this directory). |
251 | | - |
252 | | -It is also possible to download sources from each project's homepage, |
253 | | -though you may have to change the names of some folders in order to make |
254 | | -things work. For instance, if you were to download a version 5.0.7 of |
255 | | -XZ Utils, you would need to extract the archive into ..\externals\xz-5.0.5 |
256 | | -anyway, since that is where the solution is set to look for xz. The |
257 | | -same is true for all other external projects. |
258 | | - |
259 | | -The external(-amd64).bat scripts will also build a debug build of |
260 | | -Tcl/Tk, but there aren't any equivalent batch files for building release |
261 | | -versions of Tcl/Tk currently available. If you need to build a release |
262 | | -version of Tcl/Tk, just take a look at the relevant external(-amd64).bat |
263 | | -file and find the two nmake lines, then call each one without the |
264 | | -'DEBUG=1' parameter, i.e.: |
265 | | - |
266 | | -The external-amd64.bat file contains this for tcl: |
267 | | - nmake -f makefile.vc DEBUG=1 MACHINE=AMD64 INSTALLDIR=..\..\tcltk64 clean all install |
268 | | - |
269 | | -So for a release build, you'd call it as: |
270 | | - nmake -f makefile.vc MACHINE=AMD64 INSTALLDIR=..\..\tcltk64 clean all install |
271 | | - |
272 | | -Note that the above command is called from within ..\externals\tcl-8.6.1.0\win |
273 | | -(relative to this directory); don't forget to build Tk as well as Tcl! |
274 | | - |
275 | | -This will be cleaned up in the future; http://bugs.python.org/issue15968 |
276 | | -tracks adding a new tcltk.vcxproj file that will build Tcl/Tk and Tix |
277 | | -the same way the other external projects listed above are built. |
| 239 | +can be built. The easiest way to do this is to use the `build.bat` |
| 240 | +script in this directory to build Python, and pass the '-e' switch to |
| 241 | +tell it to use get_externals.bat to fetch external sources and build |
| 242 | +Tcl/Tk and Tix. To use get_externals.bat, you'll need to have |
| 243 | +Subversion installed and svn.exe on your PATH. The script will fetch |
| 244 | +external library sources from http://svn.python.org/external and place |
| 245 | +them in ..\externals (relative to this directory). |
278 | 246 |
|
279 | 247 |
|
280 | 248 | Building for AMD64 |
|
0 commit comments