On Tue, 2 Jan 2007 19:35:39 +1100, "Sisyphus" <[EMAIL PROTECTED]> wrote:
>Hi, >Some questions regarding the 64-bit build: > >1) With which version of Visual Studio was it built ? It does not use Visual Studio at all; it uses the compiler included in the Windows Platform SDK. I'm not sure of the exact release date, but you need the version of the SDK that supports "Windows 2003 SP1" to get the 64 bit compilers for x64 and IA64. I think we used the latest R2 edition: http://www.microsoft.com/downloads/details.aspx?FamilyId=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en To setup the environment you have to run: "c:\Program Files\Microsoft Platform SDK\SetEnv.cmd" /XP64 /RETAIL >2) Was it built using the standard Makefile that ships with the perl source >? ... or was it necessary to do some serious hacking in order to get it to >build ? You should be able to compile the ActivePerl sources in 64 bit mode just the same way as the 32 bit sources if you build natively. The Makefile does not support cross-compilation of the 64 bit builds in a 32 bit environment. There were a few Makefile changes, that should also be in bleadperl. I'm not sure if they have trickled down to the core 5.8.8 sources, or if they are only in the ActivePerl version. Actually, I just checked the diff, and it looks like you would need to put migrate the Makefile changes yourself if you want to compiler core 5.8.8: http://downloads.activestate.com/ActivePerl/src/5.8/AP819_diff.txt There are a few casts I added to the header files too to get rid of at least some of the warnings from the C compiler because Perl often assigns pointer differences to I32 variables. But those are just cosmetic changes suppressing the noise. Cheers, -Jan _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
