PerlApp runs on Win32, Linux, and Solaris.
perlapp (and perl2exe) seems to:
1. Scan the script.
2. Grab the scanned use and require modules/files found in @inc.
3. use some sort of self-extracting zip/tar and tarball perl, the script, associated modules, files, etc.
4. Run this executable on the host. The self-extractor (after untarring/unzipping into /temp) executes perl script.
Of course the devil is in the details :-)
The version of perl that is tarred has @inc of /temp and the local directory. The self-extractor/perl-boot-loader might be the hardest part (then again, I haven't looked for it).
Are we trying to build a multi-platform compiler, cross-platform compiler, or a free-standing executable of perl scripts? The difference (to me) being: multi-platform means win32 compiler for win32 executables, linux for linux (I think this is what is being said) cross-platform means I can build a linux executable on a win32 machine (this would be crazy, huh?) free-standing would be the sleazy method described above. I guess that could be considered multi-platform, but I don't know if it's actually a compiler.
-
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.
|