mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-09-27 18:59:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 13

Update for 2.0b1. Also add more text, to be more explicit about

Browse source 
what the dozen+ subprojects are for, which are and aren't
expected to build out of the box, and what else is needed to get
them all to build.  Also explained that Alpha configurations
don't refer to pre-beta, but to the Alpha processor!  That's
baffled me for years <0.7 wink>.
This commit is contained in:
Tim Peters 2000-07-01 00:03:43 +00:00
parent ffcc3813d8
commit 4b5fb0772e
1 changed files with 87 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

116
PCbuild/readme.txt
View file

@ -1,40 +1,98 @@
Building Python using VC++ 5.0 or 6.0 Building Python using VC++ 6.0 or 5.0
------------------------------------- -------------------------------------
This directory is used to build Python for Win32 platforms, e.g. Windows
This directory is used to build Python for Win32 platforms, 95, 98 and NT. It requires Microsoft Visual C++ 6.x or 5.x.
e.g. Windows 95, 98 and NT. It requires Microsoft Visual C++ 6.x
or 5.x.
(For other Windows platforms and compilers, see ../PC/readme.txt.) (For other Windows platforms and compilers, see ../PC/readme.txt.)
XXX There are still (Python 2.0b1) a few compiler warnings under VC6.
XXX There are likely a few more under VC5.
Unlike previous versions, there's no longer a need to copy the project Unlike older versions, there's no longer a need to copy the project files
files from the PC/vc5x subdirectory to the PCbuild directory -- they from a subdirectory of PC/ to the PCbuild directory -- they come in PCbuild.
come in PCbuild.
All you need to do is open the workspace "pcbuild.dsw" in MSVC++, All you need to do is open the workspace "pcbuild.dsw" in MSVC++, select
select the Debug or Release setting (using Set Active the Debug or Release setting (using Build -> Set Active Configuration...),
Configuration... in the Build menu), and build the projects. and build the projects.
The proper order to build is The proper order to build subprojects is:
1) python16 (this builds python16.dll and python16.lib) 1) python20 (this builds the main Python DLL and library files,
2) python (this builds python.exe) python20.{dll, lib})
3) the other subprojects
Some subprojects require that you have distributions of other 2) python (this builds the main Python executable, python.exe)
software: Tcl/Tk, bsddb and zlib. If you don't have these, you can't
build the corresponding extensions. If you do have them, you may have 3) the other subprojects, as desired or needed (note: you probably don't
to change the project settings to point to the right include files, want to build most of the other subprojects, unless you're building an
libraries etc. entire Python distribution from scratch, or specifically making changes
to the subsystems they implement; see SUBPROJECTS below)
When using the Debug setting, the output files have a _d added to When using the Debug setting, the output files have a _d added to
their name: python16_d.dll, python_d.exe, parser_d.pyd, and so on. their name: python20_d.dll, python_d.exe, parser_d.pyd, and so on.
If you want to create your own extension module DLL, there's an SUBPROJECTS
example with easy-to-follow instructions in ../PC/example/; read the -----------
file readme.txt there first. These subprojects should build out of the box. Subprojects other than the
main ones (python20, python, pythonw) generally build a DLL (renamed to
.pyd) from a specific module so that users don't have to load the code
supporting that module unless they import the module.
Pointers: python20
Python http://www.python.org .dll and .lib
Tcl/Tk http://dev.scriptics.com python
zlib http://www.winimage.com/zLibDll .exe
bsddb Sam Rushing's web/ftp site pythonw
pythonw.exe, a variant of python.exe that doesn't pop up a DOS box
_socket
socketmodule.c
_sre
Unicode-aware regular expression engine
mmap
mmapmodule.c
parser
the parser module
select
selectmodule.c
unicodedata
large tables of Unicode data
winreg
Windows registry API
winsound
play sounds (typically .wav files) under Windows
The following subprojects will generally NOT build out of the box. They
wrap code Python doesn't control, and you'll need to download the base
packages first (study the subproject structure from within MSVC to see
where each expects to find the unpacked packages):
_tkinter
Python wrapper for the Tk windowing system. Requires tcl831.exe from
http://dev.scriptics.com/software/tcltk/downloadnow83.tml
zlib
Python wrapper for the zlib compression library. Requires
http://www.winimage.com/zLibDll/zlib133dll.zip
and
ftp://ftp.uu.net/graphics/png/src/zlib133.zip
bsddb
Python wrapper for the BSD database 1.85. Requires bsddbmodule.zip,
from the bsddb link at
http://www.nightmare.com/software.html
pyexpat
Python wrapper for accelerated XML parsing. Requires
ftp://ftp.jclark.com/pub/xml/expat.zip
NOTE ON CONFIGURATIONS
----------------------
Under Build -> Configuration ..., you'll find several Alpha configurations,
such as "Win32 Alpha Release". These do not refer to alpha versions (as in
alpha, beta, final), but to the DEC/COMPAQ Alpha processor. Ignore them if
you're not building on an Alpha box.
YOUR OWN EXTENSION DDLs
-----------------------
If you want to create your own extension module DLL, there's an example
with easy-to-follow instructions in ../PC/example/; read the file
readme.txt there first.