Slashdot Mirror

← Back to Stories (view on slashdot.org)

How Well Does Perl2exe Work for Large Applications?

Posted by Cliff on from the script-is-to-executable-as-dynamic-is-to-static dept.

bobm writes "One of the issues with not using the 'standard' MS tools (VC, VB, etc) is that you face the possiblity of having to load a lot of DLL's to support an application. I'm in this boat with a Perl app I would like to migrate to a couple of Windows 2000 servers. It's a simple app that runs well on our Unix boxes and if it wasn't for the overhead of having to install perl and all of the required modules, it would be a no brainer. However I just stumbled upon Perl2Exe at Indigostar. A small app worked great and I'm wondering if anyone else has used it and how large of an app have they released? Any other pointers and info on pertinent issues would be helpful too."

3 of 51 comments (clear)

  1. My advice: Do by Mr_Silver · · Score: 4, Interesting
    Argh! Sometimes its really obvious that people who write comments like this have never deployed programs, don't think about users or perversly like using a sledgehammer to break a nut.

    For the record, I recommend using Perl2exe and avoid installing the Perl runtimes!

    I've used Perl2exe for, admitidally smaller programs, and it works great. Check out the options, you can either compile into one large exe, or use one (yes, one) additional dll and reduce the size of the program considerably.

    So basically, you have the best of both worlds. If it's only ever going to be one application, do a full binary and deal with the size. If there could be one or more, then consider using the dll.

    Yes, there are 2 downsides, one is the size of the application - but compaired to the size and hassle of installing the whole Perl distribution for every machine, it's a no-brainer.

    The other being the ability to edit the code. Well if there are individuals out there who need to edit it, they'll have the perl runtimes and you can just give them the source. But giving normal users carte blanche to edit the code is asking for hundreds of support calls.

    If options are needed code them in rather than get them to edit the source.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
  2. My experience by Boglin · · Score: 4, Interesting
    A couple of years back, I was writing a small program for language translation and I needed it to run on my classmates' Windows machines. Due to the heavy text processing nature of the project, Perl seemed like the prime choice. However, I knew there wasn't a wicket's chance in a supernova that I was going to get the end users to install Perl.

    Thus, I tried Perl2exe. There were two parts that really impressed me. First, it included all of the packages that I was using, including Perl/TK (as I said, Windows users. The looked at my initial console version like it was in Hieroglyphics.) I was also impressed that the program and dictionary could still be compressed to fit on a floppy, which was a huge relief from having to Perl burn CDs for all of the users. In the end, I would say that, if you are porting a simple maintenance script or other non-time critical application to the Win2k servers, by all means go with Perl2exe. However, if this is a critical part of your new Buzzword Server System, then read a post from someone who knows better.

  3. It can be a godsend by n9hmg · · Score: 4, Interesting

    Depending on your application, it can be an enormous help. Building the apps fully static lets you work on your application in perl, edit, run, modify, debug, enhance, run, etc. on your development machine, then slap out a binary that can be run on any other windoze machine by simply getting that machine access to the executable. You're not messing with the registry, sticking DLLs all over the place, and taking up disk space with a development system when all you need is to run the program you wrote with your development system. Sure, the individual binary is enormous, for what it does, at least, at small amounts of code (as the app grows, the overhead shrinks into insignificance).
    I had to write and run an application on a bunch of windoze boxen for a client a couple of years ago. I was not permitted to install anything. I got it working in perl, used an eval copy(it wasn't a long-term application) of perl2exe, got the job done, and everybody was happy. Sounds like your app is similar.
    One caveat: the big static binaries tend to load kind of slow, but as you know, everything has tradeoffs.