Re: ActiveState modules

Replies are listed 'Best First'.
Re^2: ActiveState modules by gellyfish (Monsignor) on Mar 03, 2005 at 12:07 UTC
It should be noted that there are some caveats when compiling extensions with a different version of the compiler than that which compiled the Perl (which is the case when building modules for ActivePerl with the Visual C++ Toolkit), this is due to the fact that the C runtime libraries will reside in different DLLs so OS level objects that might be shared between Perl and the extension that are defined in the runtime (such as `HANDLE`s and so forth) will not be valid in the part that didn't define them. I was recently caught out by this with respect to Term::ReadKey and it is discussed here Of course modules that don't share C runtime thingies with Perl shouldn't be affected by this. /J\	[reply] [d/l]
Re^3: ActiveState modules by BrowserUk (Patriarch) on Mar 03, 2005 at 12:38 UTC
A good point worth noting++ As it is, I still use the older version of VC++ (Microsoft (R) 32-bit C/C++ Standard Compiler Version 13.00.9466 for 80x86) for anything Perl related, but I'm not sure if this is still available for download anywhere? Examine what is said, not who speaks. Silence betokens consent. Love the truth but pardon error.	[reply]
Re^2: ActiveState modules by thekestrel (Friar) on Mar 02, 2005 at 23:39 UTC
Thanks BrowserUk, I have the compiler installed no problems, but apparently perl\lib\CORE\win32.h includes windows.h. From memory this is the first port of call for all windows applications and looking at samples of it on the web it basically includes the rest of the world in .h format. The cut down toolkit does not come with the windows .h plethora of files, am I right in assuming one needs the full version of Visual studio to get these or are older versions of these also proferred around somewhere? Regards Paul	[reply]
Re^3: ActiveState modules by BrowserUk (Patriarch) on Mar 03, 2005 at 00:11 UTC
From memory this is the first port of call for all windows applications You're memory is correct. I already had those header files from an earlier install. You probably need to get this (108 MB!), but that also has this (23MB) as a pre-requisite. Examine what is said, not who speaks. Silence betokens consent. Love the truth but pardon error.	[reply]
Re^4: ActiveState modules by thekestrel (Friar) on Mar 03, 2005 at 23:37 UTC
BrowerUK, Alas, 140Meg of SDK does not seem to include the standard windows include files? looks like they only have the basics ...math.h conio.h etc, but no windows headers? Maybe I'll have to try another compiler I'm not so sure I won't end up having to buy something to get where I want with microsoft. I believe Watcom is now free and they had windows compatibility, but I'm guessing that will probably mean buggerizing around with flags if they differ from compiler to compiler (crosses fingers they don't) Regards Paul	[reply]
Re^5: ActiveState modules by BrowserUk (Patriarch) on Mar 04, 2005 at 00:20 UTC
Re^4: ActiveState modules by thekestrel (Friar) on Mar 05, 2005 at 03:55 UTC
There is a better way =).... I've installed Cygwin and then the perl, make, gcc options etc and now I can't pretty nuch build any CPAN module like I was on a *nix box which is great. Regards Paul	[reply]