... does this mean I should be installing the Microsoft Windows SDK for Windows 7 instead?
I don't think so. Assuming you're going to be using your compiler with ActivePerl, you (ideally) want the same compiler that built ActivePerl - which is the one that I gave the link to.
My PC is not a server at all, and the operating system is Vista (64 bit), yet that compiler works fine with the w64 builds of ActivePerl.
Cheers,
Rob | [reply] |
That link redirects me to install Windows SDK for Windows Server 2008 and .NET Framework 3.5 - do you believe that this is still OK?
| [reply] |
That link redirects me to install Windows SDK for Windows Server 2008 and .NET Framework 3.5
Bastards !!
It's not the same compiler as was used to build ActivePerl. I don't think it uses the same runtime (msvcrt.dll) as used by 2003 R2, and that can pose a problem in certain situations. Those situations are not common - but that's no consolation if you're wanting to build one of the modules that *are* affected by this. I think you'll also need to remove 'bufferoverflowu.lib' from the 'libs' and 'perllibs' entries in perl/lib/config_heavy.pl - though that's not such a big deal. If you can track down the one I specified (which, I think, is still available) it would be better. Maybe go to http://www.microsoft.com and try a search there for it.
But if you can't find the "2003 R2" then go with the one you've been re-directed to. (I think BrowserUk uses that one - with good results. I'll /msg him and ask him to correct me if I'm wrong about that.)
Another approach would be to install that 2008 version and then use it to build your own perl from source.
Cheers,
Rob
| [reply] |