On Thu, 28 May 2009, Sisyphus wrote: > ----- Original Message ----- > From: "Jan Dubois" <j...@activestate.com> > >>> It's important that I don't lose the 2003 version, as it seems to be >>> no longer readily available from MS. (All links to it quickly turn >>> into links to the 2008 version when it comes to strating a >>> download.) >> >> Really? I didn't have any problems finding and downloading it so far: >> http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en > > On that page, just below the "Overview" heading I see the following note: > > NOTE: This version of the Platform SDK has been superceded by the Windows > SDK for Windows Server 2008 and .NET Framework 3.5. > > And the "Web Install" link leads to > http://www.microsoft.com/downloads/details.aspx?FamilyId=E6E1C3DF-A74F-4207-8586-711EBE331CDC&displaylang=en > which offers a "Windows SDK for Windows Server 2008 and .NET Framework 3.5" > download. > > The "DVD ISO image" link also leads to "Windows SDK for Windows Server 2008 > and .NET Framework 3.5".
Yes, as the text says, these are all helpful pointers to the latest releases. > Or ... have I misinterpreted what I'm seeing there ? (Perhaps the "continue" > link still leads to the installation of the SDK 2003 ?) Indeed, the "Continue" button is exactly what you have to press. It does its usual Windows Genuine Advantage verification and then lets you install the SDK, [...] > > The advantage of the 2003 SDK compiler for x64 (and VC6 for x86) is > > that they don't require additional runtime libraries; they link > > against MSVCRT.dll which is already part of Windows. So any > > application generated with PAR / PerlApp / Perl2Exe doesn't need to > > bundle MSVCR80.dll. > > > > Yes, this is a good reason for using that particular compiler to build perl. > As long as that compiler remains readily available, I see no cause for > concern. Well, VC6 is no longer available if you don't already have it. You can still generate compatible binaries with MinGW, which will also link against MSVCRT.dll, or you can use a later VC version, but then you'll need to also use the version specific runtime library as well, which also works as long as you are careful not to mix runtime objects, e.g. don't call msvcr80.free() on a pointer that you received from msvcrt.malloc(), or call msvcrt.fread() on a FILE* that you received from msvcr80.fopen(). Cheers, -Jan _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
