----- 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". Or ... have I misinterpreted what I'm seeing there ? (Perhaps the "continue" link still leads to the installation of the SDK 2003 ?) > > Yes, they install into different directories. The 2003 version is even > still > called the "Platform SDK" while the 2008 version is now called the > "Windows SDK". > > You can install multiple SDKs on the same machine; just make sure you > don't let > it set up environment variables automatically but use the setenv.cmd for > each > version as you need it. Excellent news - I'll get started on it soon. > >> On an on-topic note .... does the unavailability of the 2003 version mean >> that, at some stage, it will be no longer used to build the x64 versions >> of >> ActivePerl ? [snip] > 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. Thanks, Jan. Cheers, Rob _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
