comment on

Hmmm, you might want to check out par.

#> pp -o packed.exe source.pl        
# creates a self-contained binary.

Modules can reside in different directories in a PAR file:

        /                       # casual packaging only
        /lib/                   # standard location
        /arch/                  # for creating from blib/ 
        /i386-freebsd/          # i.e. $Config{archname}
        
Par was tested on Win32, FreeBSD, Linux, AIX, Solaris with Perl 5.6.1 
+and 5.8.0.
[download]

It has truckloads of more options according to these pages, you might want to check out the newest version of par anyway, since it seems to do everything perl2exe does (even more I think).

Oh, and did I mention it was free (unlike perl2exe)?

Teabag
Sure there's more than one way, but one just needs one anyway - Teabag

In reply to Re: perl2exe question by teabag
in thread perl2exe question by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks