At 05:43 PM 12/29/03 +0100, Martin v. Loewis wrote: OTOH, I cannot see what the problem might be - except that you will
have to link with msvcr71.dll at the end, not with msvcrt40.dll.
If this hasn't been resolved, and somebody can send me a binary for a .NET-built Python, I'll be happy to test.
Sure: Please try my installer at
http://www.dcl.hpi.uni-potsdam.de/home/loewis/python2.4.0.msi
Notice that this doesn't include msvcr71.dll, which I could provide in private.
Please do.
It also does not include msvcr71.lib - I have no clue how you would get a copy of that. But then, somehow, msvcrt40.lib (or is it msvcrt40.a) must have gotten into mingw32 also.
Actually, one generates that by using dlltool and various other programs to extract a .def file from python2x.dll. I haven't generated one in ages, so I'm going to have to dig back up how to do that. The rest is handled by the distutils, pretty much. I don't think there's actually any direct linking to the MS VC runtime, anyway, if one is only using Python API calls. But I guess I'll find out. Hopefully I'll have enough clock cycles to spare on Thursday to get everything set up and tested.