[Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Wed Jan 21 20:42:17 CET 2009
- Previous message: [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
- Next message: [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
sorry, martin - i thought the win32 builds generated python25.lib, python25.dll
Correct.
and python25.def
No.
so as to fit into the 8.3 filename convention.
No. It generates python25.lib because that's the import library for python25.dll. It calls it python25.dll because the lib prefix is atypical for the platform, and also redundant (DLL means "dynamic link library").
The Python binary installer also includes libpython25.a, for use with mingw32.
Regards, Martin
- Previous message: [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
- Next message: [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]