RELEASED Python 2.4, alpha 1

[Mike C. Fletcher]

Martin v. Löwis wrote:

> Mike C. Fletcher wrote:
>
>> Anyway, for now I need to get to bed, so I suppose I'll pick this up 
>> some other day.  Main message is, don't discount the possibility of 
>> building with the Toolkit just yet.  Have fun,
>
>
> Can you check what CRT your extension modules are linked with?
> You can use depends.exe or dumpbin.exe /all to find out.
>
> Python might seriously break if you combine different versions
> of the CRT, so you really need to link with msvcr71.dll: not
> msvcrt.dll, not crtdll.dll, and not msvcrt40.dll (and neither
> msvcr70.dll). Linking with a static libc.lib is also incorrect.

Well, isn't that a PITA.  The MS Toolkit compiler is linking against 
msvcrt.dll, not msvcr71.dll.  Apparently it's picking up the Visual 
Studio 6.0 msvcrt.lib which is then pointing it to the wrong DLL, while 
the free compiler and the SDK do not include msvcrt.lib .  Okay, 
searching about, I find that there's apparently a legal source for 
msvcrt.lib, namely the .NET Framework SDK...

    http://sapdb.2scale.net/moin.cgi/MS_20C_2b_2b_20Toolkit

So, I take a few minutes to download that (it's only 100MB or so)...
Then add the lib directory to my vc7.bat file's lib environmental 
parameter...
And rebuild...

And now depends says the module is linked against msvcr71.dll .  There 
are apparently other missing headers/libs for the MS Toolkit compiler 
(see link above), but I'll plan to cross those bridges when I have more 
time for bridge-building :) .

Have fun,
Mike

________________________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://members.rogers.com/mcfletch/
  blog: http://zope.vex.net/~mcfletch/plumbing/