Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 1 | Building Python using VC++ 6.0 or 5.0 |
Guido van Rossum | a29b360 | 2000-03-29 01:51:37 +0000 | [diff] [blame] | 2 | ------------------------------------- |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 3 | This directory is used to build Python for Win32 platforms, e.g. Windows |
| 4 | 95, 98 and NT. It requires Microsoft Visual C++ 6.x or 5.x. |
Guido van Rossum | 15b239f | 1998-05-26 14:16:23 +0000 | [diff] [blame] | 5 | (For other Windows platforms and compilers, see ../PC/readme.txt.) |
| 6 | |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 7 | All you need to do is open the workspace "pcbuild.dsw" in MSVC++, select |
| 8 | the Debug or Release setting (using Build -> Set Active Configuration...), |
| 9 | and build the projects. |
Guido van Rossum | 15b239f | 1998-05-26 14:16:23 +0000 | [diff] [blame] | 10 | |
Tim Peters | befc97c | 2001-01-18 19:01:39 +0000 | [diff] [blame] | 11 | The proper order to build subprojects: |
Guido van Rossum | 15b239f | 1998-05-26 14:16:23 +0000 | [diff] [blame] | 12 | |
Tim Peters | 97c9640 | 2001-01-17 23:23:13 +0000 | [diff] [blame] | 13 | 1) pythoncore (this builds the main Python DLL and library files, |
Tim Peters | befc97c | 2001-01-18 19:01:39 +0000 | [diff] [blame] | 14 | python21.{dll, lib} in Release mode) |
| 15 | NOTE: in previous releases, this subproject was |
| 16 | named after the release number, e.g. python20. |
Guido van Rossum | 15b239f | 1998-05-26 14:16:23 +0000 | [diff] [blame] | 17 | |
Tim Peters | befc97c | 2001-01-18 19:01:39 +0000 | [diff] [blame] | 18 | 2) python (this builds the main Python executable, |
| 19 | python.exe in Release mode) |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 20 | |
| 21 | 3) the other subprojects, as desired or needed (note: you probably don't |
| 22 | want to build most of the other subprojects, unless you're building an |
| 23 | entire Python distribution from scratch, or specifically making changes |
| 24 | to the subsystems they implement; see SUBPROJECTS below) |
Guido van Rossum | 15b239f | 1998-05-26 14:16:23 +0000 | [diff] [blame] | 25 | |
| 26 | When using the Debug setting, the output files have a _d added to |
Tim Peters | 97c9640 | 2001-01-17 23:23:13 +0000 | [diff] [blame] | 27 | their name: python21_d.dll, python_d.exe, parser_d.pyd, and so on. |
Guido van Rossum | e79cf32 | 1998-07-07 22:35:03 +0000 | [diff] [blame] | 28 | |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 29 | SUBPROJECTS |
| 30 | ----------- |
Tim Peters | 610a827 | 2000-07-01 02:51:23 +0000 | [diff] [blame] | 31 | These subprojects should build out of the box. Subprojects other than the |
Tim Peters | befc97c | 2001-01-18 19:01:39 +0000 | [diff] [blame] | 32 | main ones (pythoncore, python, pythonw) generally build a DLL (renamed to |
Tim Peters | 610a827 | 2000-07-01 02:51:23 +0000 | [diff] [blame] | 33 | .pyd) from a specific module so that users don't have to load the code |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 34 | supporting that module unless they import the module. |
Guido van Rossum | e79cf32 | 1998-07-07 22:35:03 +0000 | [diff] [blame] | 35 | |
Tim Peters | 97c9640 | 2001-01-17 23:23:13 +0000 | [diff] [blame] | 36 | pythoncore |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 37 | .dll and .lib |
| 38 | python |
| 39 | .exe |
| 40 | pythonw |
| 41 | pythonw.exe, a variant of python.exe that doesn't pop up a DOS box |
| 42 | _socket |
| 43 | socketmodule.c |
| 44 | _sre |
| 45 | Unicode-aware regular expression engine |
Tim Peters | b16c56f | 2001-02-02 21:24:51 +0000 | [diff] [blame] | 46 | _symtable |
| 47 | the _symtable module, symtablemodule.c |
Tim Peters | d66595f | 2001-02-04 03:09:53 +0000 | [diff] [blame] | 48 | _testcapi |
Tim Peters | b16c56f | 2001-02-02 21:24:51 +0000 | [diff] [blame] | 49 | tests of the Python C API, run via Lib/test/test_capi.py, and |
Tim Peters | d66595f | 2001-02-04 03:09:53 +0000 | [diff] [blame] | 50 | implemented by module Modules/_testcapimodule.c |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 51 | mmap |
| 52 | mmapmodule.c |
| 53 | parser |
| 54 | the parser module |
Tim Peters | b012a15 | 2002-02-13 23:56:46 +0000 | [diff] [blame] | 55 | pyexpat |
| 56 | Python wrapper for accelerated XML parsing, which incorporates stable |
| 57 | code from the Expat project: http://sourceforge.net/projects/expat/ |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 58 | select |
| 59 | selectmodule.c |
Tim Peters | 19f52c2 | 2001-01-24 10:07:22 +0000 | [diff] [blame] | 60 | unicodedata |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 61 | large tables of Unicode data |
| 62 | winreg |
| 63 | Windows registry API |
| 64 | winsound |
| 65 | play sounds (typically .wav files) under Windows |
| 66 | |
| 67 | The following subprojects will generally NOT build out of the box. They |
| 68 | wrap code Python doesn't control, and you'll need to download the base |
Tim Peters | aff1284 | 2000-08-25 06:52:44 +0000 | [diff] [blame] | 69 | packages first and unpack them into siblings of PCbuilds's parent |
| 70 | directory; for example, if your PCbuild is .......\dist\src\PCbuild\, |
| 71 | unpack into new subdirectories of dist\. |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 72 | |
| 73 | _tkinter |
Tim Peters | aff1284 | 2000-08-25 06:52:44 +0000 | [diff] [blame] | 74 | Python wrapper for the Tk windowing system. Requires tcl832.exe from |
Tim Peters | 610a827 | 2000-07-01 02:51:23 +0000 | [diff] [blame] | 75 | http://dev.scriptics.com/software/tcltk/downloadnow83.html |
Tim Peters | aff1284 | 2000-08-25 06:52:44 +0000 | [diff] [blame] | 76 | Run the installer, forcing installation into dist\Tcl. |
| 77 | Be sure to install everything, including the Tcl/Tk header files. |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 78 | |
| 79 | zlib |
Tim Peters | ee826f8 | 2001-01-31 19:39:44 +0000 | [diff] [blame] | 80 | Python wrapper for the zlib compression library. Get the source code |
Tim Peters | 6077f64 | 2002-03-13 21:51:55 +0000 | [diff] [blame] | 81 | for version 1.1.4 from a convenient mirror at: |
| 82 | http://www.gzip.org/zlib/ |
| 83 | Unpack into dist\zlib-1.1.4. |
Tim Peters | ee826f8 | 2001-01-31 19:39:44 +0000 | [diff] [blame] | 84 | A custom pre-link step in the zlib project settings should manage to |
Tim Peters | 6077f64 | 2002-03-13 21:51:55 +0000 | [diff] [blame] | 85 | build zlib-1.1.4\zlib.lib by magic before zlib.pyd (or zlib_d.pyd) is |
Tim Peters | ee826f8 | 2001-01-31 19:39:44 +0000 | [diff] [blame] | 86 | linked in PCbuild\. |
| 87 | However, the zlib project is not smart enough to remove anything under |
Tim Peters | 6077f64 | 2002-03-13 21:51:55 +0000 | [diff] [blame] | 88 | zlib-1.1.4\ when you do a clean, so if you want to rebuild zlib.lib |
| 89 | you need to clean up zlib-1.1.4\ by hand. |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 90 | |
Tim Peters | b0ead4e | 2002-11-09 04:48:58 +0000 | [diff] [blame] | 91 | bz2 |
| 92 | Python wrapper for the libbz2 compression library. Homepage |
| 93 | http://sources.redhat.com/bzip2/ |
| 94 | Download the source tarball, bzip2-1.0.2.tar.gz. |
| 95 | Unpack into dist\bzip2-1.0.2. WARNING: If you using WinZip, you |
| 96 | must disable its "TAR file smart CR/LF conversion" feature (under |
| 97 | Options -> Configuration -> Miscellaneous -> Other) for the duration. |
| 98 | Don't bother trying to use libbz2.dsp with MSVC. After 10 minutes |
| 99 | of fiddling, I couldn't get it to work. Perhaps it works with |
| 100 | MSVC 5 (I used MSVC 6). It's better to run the by-hand makefile |
| 101 | anyway, because it runs a helpful test step at the end. |
| 102 | cd into dist\bzip2-1.0.2, and run |
| 103 | nmake -f makefile.msc |
| 104 | [Note that if you're running Win9X, you'll need to run vcvars32.bat |
| 105 | before running nmake (this batch file is in your MSVC installation). |
| 106 | TODO: make this work like zlib (in particular, MSVC runs the prelink |
| 107 | step in an enviroment that already has the correct envars set up). |
| 108 | ] |
| 109 | The make step should yield any warnings or errors, and should end |
| 110 | by displaying 6 blocks each terminated with |
| 111 | FC: no differences encountered |
| 112 | If FC finds differences, see the warning abou WinZip above (when I |
| 113 | first tried it, sample3.ref failed due to CRLF conversion). |
| 114 | All of this managed to build bzip2-1.0.2\libbz2.lib, which the Python |
| 115 | project links in. |
| 116 | |
| 117 | |
| 118 | |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 119 | bsddb |
Tim Peters | 610a827 | 2000-07-01 02:51:23 +0000 | [diff] [blame] | 120 | Python wrapper for the BSD database 1.85. Requires db.1.85.win32.zip, |
| 121 | from the "bsd db" link at |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 122 | http://www.nightmare.com/software.html |
Tim Peters | aff1284 | 2000-08-25 06:52:44 +0000 | [diff] [blame] | 123 | Unpack into dist\bsddb. |
| 124 | You then need to compile it: cd to dist\bsddb\Port\win32, and run |
| 125 | nmake -f makefile_nt.msc |
| 126 | This builds bsddb\Port\win32\db.lib, which the MSVC project links in. |
| 127 | Note that if you're running Win9X, you'll need to run vcvars32.bat |
| 128 | before running nmake (this batch file is in your MSVC installation). |
Tim Peters | ca873ed | 2001-02-01 05:10:02 +0000 | [diff] [blame] | 129 | TODO: make this work like zlib (in particular, MSVC runs the prelink |
| 130 | step in an enviroment that already has the correct envars set up). |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 131 | |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 132 | |
Tim Peters | f9a4a6e | 2000-07-01 20:38:27 +0000 | [diff] [blame] | 133 | YOUR OWN EXTENSION DLLs |
Tim Peters | 4b5fb07 | 2000-07-01 00:03:43 +0000 | [diff] [blame] | 134 | ----------------------- |
| 135 | If you want to create your own extension module DLL, there's an example |
| 136 | with easy-to-follow instructions in ../PC/example/; read the file |
| 137 | readme.txt there first. |