On Tue, 15 Jul 2003 19:47:26 -0700, "Dave Roth" <[EMAIL PROTECTED]> wrote:
>Yikes. I don't wanna rely on .Net framework!!!! Yikes! You don't rely on the .NET Framework. I was only suggesting this as it contains the MSVCR70.DLL (and the non-optimizing commandline VC++ 7.0 compiler). >Hmm. There has to be some library that I can statically link to. You probably can, but you would end up with multiple C runtime systems at runtime, which can create problems with structured exception handling (yes, you would have the same problem when linking in MSVCR70.DLL). If at all possible, I would recommend building Perl modules with VC++ 6.0. Cheers, -Jan PS: I spent a few hours trying to trick VC++ 7.0 to just use MSVCRT.DLL, but there are a few places where the compiler generates calls to internal function only supported by MSVCR70.DLL. You are welcome to argue this with the C++ compiler team. They seem to believe having to redistribute a C runtime again is progress. :( _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
