1- Building Python using VC++ 6.0 or 5.0
1+ Building Python using VC++ 7.1
22-------------------------------------
33This 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.
4+ 95, 98 and NT. It requires Microsoft Visual C++ 7.1
5+ (a.k.a. Visual Studio .NET 2003).
56(For other Windows platforms and compilers, see ../PC/readme.txt.)
67
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.
8+ All you need to do is open the workspace "pcbuild.sln " in MSVC++, select
9+ the Debug or Release setting (using "Solution Configuration" from
10+ the "Standard" toolbar"), and build the projects.
1011
1112The proper order to build subprojects:
1213
@@ -24,7 +25,7 @@ The proper order to build subprojects:
2425 to the subsystems they implement; see SUBPROJECTS below)
2526
2627When using the Debug setting, the output files have a _d added to
27- their name: python21_d .dll, python_d.exe, parser_d.pyd, and so on.
28+ their name: python24_d .dll, python_d.exe, parser_d.pyd, and so on.
2829
2930SUBPROJECTS
3031-----------
@@ -83,16 +84,16 @@ _tkinter
8384 Go to
8485 http://prdownloads.sourceforge.net/tcl/
8586 and download
86- tcl843 -src.zip
87- tk843 -src.zip
87+ tcl845 -src.zip
88+ tk845 -src.zip
8889 Unzip into
89- dist\tcl8.4.3 \
90- dist\tk8.4.3 \
90+ dist\tcl8.4.5 \
91+ dist\tk8.4.5 \
9192 respectively.
9293
9394 Build Tcl first (done here w/ MSVC 6 on Win98SE)
9495 ---------------
95- cd dist\tcl8.4.3 \win
96+ cd dist\tcl8.4.5 \win
9697 run vcvars32.bat [necessary even on Win2K]
9798 nmake -f makefile.vc
9899 nmake -f makefile.vc INSTALLDIR=..\..\tcl84 install
@@ -107,9 +108,9 @@ _tkinter
107108
108109 Build Tk
109110 --------
110- cd dist\tk8.4.3 \win
111- nmake -f makefile.vc TCLDIR=..\..\tcl8.4.3
112- nmake -f makefile.vc TCLDIR=..\..\tcl8.4.3 INSTALLDIR=..\..\tcl84 install
111+ cd dist\tk8.4.5 \win
112+ nmake -f makefile.vc TCLDIR=..\..\tcl8.4.5
113+ nmake -f makefile.vc TCLDIR=..\..\tcl8.4.5 INSTALLDIR=..\..\tcl84 install
113114
114115 XXX Should we compile with OPTS=threads?
115116
160161 FC: no differences encountered
161162 If FC finds differences, see the warning abou WinZip above (when I
162163 first tried it, sample3.ref failed due to CRLF conversion).
164+
165+ # XXX: it fails with vc 7.1, so the tests are skipped for now.
163166
164167 All of this managed to build bzip2-1.0.2\libbz2.lib, which the Python
165168 project links in.
@@ -169,35 +172,36 @@ _bsddb
169172 Go to Sleepycat's download page:
170173 http://www.sleepycat.com/download/
171174
172- and download version 4.1.25 . The file name is db-4.1.25 .NC.zip.
175+ and download version 4.2.42 . The file name is db-4.2.52 .NC.zip.
173176 XXX with or without strong cryptography? I picked "without".
174177
175178 Unpack into
176- dist\db-4.1.25
179+ dist\db-4.2.52
177180
178- [If using WinZip to unpack the db-4.1.25 .NC distro, that requires
181+ [If using WinZip to unpack the db-4.2.52 .NC distro, that requires
179182 renaming the directory (to remove ".NC") after unpacking.
180183 ]
181184
182185 Open
183- dist\db-4.1.25 \docs\index.html
186+ dist\db-4.2.52 \docs\index.html
184187
185188 and follow the Windows instructions for building the Sleepycat
186189 software. Note that Berkeley_DB.dsw is in the build_win32 subdirectory.
187190 Build the Release version ("build_all -- Win32 Release").
188191
189- XXX We're actually linking against Release_static\libdb41s .lib.
192+ XXX We're actually linking against Release_static\libdb42s .lib.
190193 XXX This yields the following warnings:
191194"""
192195Compiling...
193196_bsddb.c
194197Linking...
195198 Creating library ./_bsddb.lib and object ./_bsddb.exp
196- LINK : warning LNK4049: locally defined symbol "_malloc" imported
197- LINK : warning LNK4049: locally defined symbol "_free" imported
198- LINK : warning LNK4049: locally defined symbol "_fclose" imported
199- LINK : warning LNK4049: locally defined symbol "_fopen" imported
200- _bsddb.pyd - 0 error(s), 4 warning(s)
199+ _bsddb.obj : warning LNK4217: locally defined symbol _malloc imported in function __db_associateCallback
200+ _bsddb.obj : warning LNK4217: locally defined symbol _free imported in function __DB_consume
201+ _bsddb.obj : warning LNK4217: locally defined symbol _fclose imported in function _DB_verify
202+ _bsddb.obj : warning LNK4217: locally defined symbol _fopen imported in function _DB_verify
203+ _bsddb.obj : warning LNK4217: locally defined symbol _strncpy imported in function _init_pybsddb
204+ __bsddb - 0 error(s), 5 warning(s)
201205"""
202206 XXX This isn't encouraging, but I don't know what to do about it.
203207
238242 http://www.openssl.org
239243
240244 You (probably) don't want the "engine" code. For example, get
241- openssl-0.9.6g .tar.gz
245+ openssl-0.9.7c .tar.gz
242246 not
243- openssl-engine-0.9.6g .tar.gz
247+ openssl-engine-0.9.7c .tar.gz
244248
245249 Unpack into the "dist" directory, retaining the folder name from
246250 the archive - for example, the latest stable OpenSSL will install as
273277 Win9x note: If, near the start of the build process, you see
274278 something like
275279
276- C:\Code\openssl-0.9.6g >set OPTS=no-asm
280+ C:\Code\openssl-0.9.7c >set OPTS=no-asm
277281 Out of environment space
278282
279283 then you're in trouble, and will probably also see these errors near
0 commit comments