[Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now (original) (raw)
Luke Kenneth Casson Leighton lkcl at lkcl.net
Wed Jan 21 12:10:38 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 ]
On Tue, Jan 20, 2009 at 9:19 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
That's a non-starter for anyone who incorporates Python in an existing MSVC-based development environment.
surely incorporating libpython2.5.dll.a or libpython2.6.dll.a, along with the .def and the importlib that's generated with dlldump, unless i'm missing something, would be a simple matter, yes? Not exactly sure what this is, but I believe Python already includes such a thing.
sorry, martin - i thought the win32 builds generated python25.lib, python25.dll and python25.def so as to fit into the 8.3 filename convention.
- 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 ]