FAQ 3.21 How can I compile my Perl program into byte code or C?

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.


3.21: How can I compile my Perl program into byte code or C?

    (contributed by brian d foy)

    In general, you can't do this. There are some things that may work for
    your situation though. People usually ask this question because they
    want to distribute their works without giving away the source code, and
    most solutions trade disk space for convenience. You probably won't see
    much of a speed increase either, since most solutions simply bundle a
    Perl interpreter in the final product (but see "How can I make my Perl
    program run faster?").

    The Perl Archive Toolkit (http://par.perl.org/index.cgi ) is Perl's
    analog to Java's JAR. It's freely available and on CPAN

    The B::* namespace, often called "the Perl compiler", but is really a
    way for Perl programs to peek at its innards rather than create
    pre-compiled versions of your program. However. the B::Bytecode module
    can turn your script into a bytecode format that could be loaded later
    by the ByteLoader module and executed as a regular Perl script.

    There are also some commercial products that may work for you, although
    you have to buy a license for them.

    The Perl Dev Kit (http://www.activestate.com/Products/Perl_Dev_Kit /)
    from ActiveState can "Turn your Perl programs into ready-to-run
    executables for HP-UX, Linux, Solaris and Windows."

    Perl2Exe (http://www.indigostar.com/perl2exe.htm ) is a command line
    program for converting perl scripts to executable files. It targets both
    Windows and unix platforms.


Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short.  They represent an important
part of the Usenet tradition.  They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.

If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile.  If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.

Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release.  It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.

The perlfaq manual page contains the following copyright notice.


    Copyright (c) 1997-2002 Tom Christiansen and Nathan
    Torkington, and other contributors as noted. All rights

This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.

Site Timeline