directories instead.\r
\r
\r
-Microsoft Visual C++ Version 4.0 (32-bit Windows)\r
+Microsoft Visual C++ Version 4.x (32-bit Windows)\r
=================================================\r
\r
-(While we have done all our testing with VC version 4.0, we are\r
-confident that the same procedure will work for versions 4.1 and 4.2.)\r
+(For historic reasons this uses the filename "vc40"; it has been tested\r
+most recently with VC 4.2. VC 5.x should be able to convert it.)\r
\r
The distributed Makefile is vc40.mak. This file is distributed with\r
CRLF line separators, otherwise Developer Studio won't like it. It\r
project. The project contains six targets, which should be built in\r
this order:\r
\r
-python14 The Python core as a DLL, named python14.dll.\r
+python15 The Python core as a DLL, named python15.dll.\r
\r
python The Python main program, named python.exe. This should\r
work as a console program under Windows 95 or NT, as well\r
as under Windows 3.1(1) when using win32s. It uses\r
- python14.dll.\r
+ python15.dll.\r
\r
_tkinter The optional _tkinter extension, _tkinter.dll; see below.\r
\r
vc40 (which Developer Studio creates); object files are placed in\r
vc40/tmp. There are no separate Release and Debug project variants.\r
Note that the python and _tkinter projects require that the\r
-python14.lib file exists in the vc40 subdirectory before they can be\r
+python15.lib file exists in the vc40 subdirectory before they can be\r
built.\r
\r
*** How to build the _tkinter extension ***\r
Additional files and subdirectories for 32-bit Windows\r
======================================================\r
\r
-python_nt.def Exports definition file for python14.dll.\r
+python_nt.def Exports definition file for python15.dll.\r
\r
-python_nt.rc Resource compiler input for python14.dll.\r
+python_nt.rc Resource compiler input for python15.dll.\r
\r
dl_nt.c, getpath_nt.c, import_nt.c\r
Additional sources used for 32-bit Windows features.\r