Nilson Santos Figueiredo Junior wrote: > On 6/30/06, Hugh Lampert <[EMAIL PROTECTED]> wrote: >> The hassle is that we are a Windows shop and my boss only cares about >> results. To roll out an .ASP application is only a matter of using the >> resources that are already installed in the development environment and >> on the production server (IIS, SQL Server 2000, etc.), so I'm already on >> thin ice with Apache and perl - although I've argued I can code more >> efficiently in perl than in the .NET environment. If I have to >> radically alter the production server beyond Perl and Apache/mod_perl >> then the limb I am going out on will bend substantially more. > > If you've already got a .NET environment then why don't you use for > compiling Perl modules? It's a much better choice than GCC when under > Windows since VS is the default compiler for AS Perl. GCC is used as a > fallback method since buying VS just for the C compiler is a little > overkill.
Don't do that. Bad things will happen. Always compiled your modules with the same compiler used for the perl install itself on Windows. To that point, you could compile perl in .NET, then do the modules that way too. -=Chris
signature.asc
Description: OpenPGP digital signature
_______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
