http://qs321.pair.com?node_id=503398


in reply to FastCGI and EXEs under Windows

There should be no reason it can't - fastcgi on IIS handles compiled C .EXE files all the time - but there may be a good reason why you can't generate proper exe files. Quoting from the CGI::Fast docs:

In addition, you'll need a version of the Perl interpreter that has been linked with the FastCGI I/O library. Precompiled binaries are available for several platforms, including DEC Alpha, HP-UX and SPARC/Solaris, or you can rebuild Perl from source with patches provided in the FastCGI developer's kit. The FastCGI Perl interpreter can be used in place of your normal Perl without ill consequences.

The activestate builds I've got my hands on are not linked with the FastCGI I/O library. You'll either have to find a library that does the FastCGI stuff in perl (shouldn't be /too/ hard a standard to do all in perl) or you'll have to rebuild ActivePerl with the FastCGI stuff linked in.

Update: Never mind - you'll just need an ActiveState version of the FCGI module, and you'll have to make sure that PerlApp includes that module in the generated EXE file.
--
@/=map{[/./g]}qw/.h_nJ Xapou cets krht ele_ r_ra/; map{y/X_/\n /;print}map{pop@$_}@/for@/