1.5.2c1 will not compile on Windows NT SP4 with VC++ 6.0 SP1

Barry Scott barry at scottbb.demon.co.uk
Sat Apr 10 13:37:49 EDT 1999


I extracted the 1.5.2c1 kit into P:\

python15 error
--------------------
VC++ 6.0 gives this error.

Fatal error C1083: Cannot open source file:
'P:\Python-1.5.2c1\Modules\reopmodule.c': No such file or directory

The file reopmodule.c is not in the kit.

Having removed reopmodule.c from the project I get a link error

LINK : fatal error LNK1104: cannot open file ".\PC\python_nt.def"

This file is also missing.

Removing python_nt.def from the project reveals files that need to be added
to the project:

    object\bufferobject.c
    pc\initwinsound.c
    modules\_localemodule.c

LINK needs winmm.lib added to it.

Now I get a python15 built.

pyhon error
----------------
The project cannot find python.c

fatal error C1083: Cannot open source file:
'P:\Python-1.5.2c1\python\Modules\python.c': No such file or directory

There is a extra "python" directory that is not in the kits layout.
Fixed by replacing with 'P:\Python-1.5.2c1\Modules\python.c'

Same path problem with python15.lib.
Fixed by replacing with P:\Python-1.5.2c1\vc40\python15.lib

Now I get a python.exe

_tkinter
----------
The tk and tcl libs are named tk80.lib and tcl80.lib not tk80vc.lib and
tcl80vc.lib.

I used the Tcl/Tk that the 1.5.2c1 installation put on my system.

Now I have _tkinter.dll

How was the kit for Windows built given all the missing or misnamed files?
Or is this a side effect of using VC++ 6.0?

I also notice that the python.exe was built 8 apr 1999 but report sa dated
of 12 Mar 1999
on the interactive command line.

        BArry






More information about the Python-list mailing list