A CGI script by itself is incomplete -- it expects a web server of some sort to open a socket, accept a connection, parse HTTP headers, populate environmental variables and send data back to the client. Compiling or rewriting your CGI script doesn't obviate the need for something to handle the HTTP side of the equation.

There are three solutions:

• Install a web server on each machine. This can be pure-Perl, like dhttp or Jellybean, or the old standby of Apache or PWS, or even the one from Indigo Perl.
• Rewrite your application not to speak HTML/CGI. Add an interface, whether Curses, Tk, GTK, QT, Win32, or what have you.
• Add some client-side processing with JavaScript to offload work from the server. Tough to do securely, maybe hard to do in a cross-platform, standards-respecting manner.

So, you're right. There's not an easy way to do what you ask. There are several alternative paths that are not too odious.