Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Linking scripts and interpreters into an executable jkahrs@castor.atlas.de (Juergen Kahrs) (1998-07-30) |
| Re: Linking scripts and interpreters into an executable rpereda@ringer.cs.utsa.edu (Ray Pereda) (1998-08-10) |
| Re: Linking scripts and interpreters into an executable Juergen.Kahrs@t-online.de (1998-08-10) |
| Re: Linking scripts and interpreters into an executable bob@netwrench.com (1998-08-13) |
| Re: Linking scripts and interpreters into an executable dan@control.com (1998-08-13) |
| Re: Linking scripts and interpreters into an executable aeb@saltfarm.bt.co.uk (Tony Bass) (1998-08-16) |
| Re: Linking scripts and interpreters into an executable jkahrs@castor.atlas.de (Juergen Kahrs) (1998-08-17) |
| From: | dan@control.com |
| Newsgroups: | comp.compilers |
| Date: | 13 Aug 1998 22:01:35 -0400 |
| Organization: | Deja News - The Leader in Internet Discussion |
| References: | 98-07-238 98-08-046 |
| Keywords: | interpreter |
Ray Pereda <rpereda@ringer.cs.utsa.edu> wrote:
> The perl people have a program that creates standalone executable
> perl programs. When I asked the author what was his technique he
> said that he did not want to make it public. Bastud.
Python has a standard utility called 'freeze' that does much of what
you want. It creates two C files that include the Python interpreter
and the compiled bytecode of the application and a Makefile to link
them up. Works on Unix, Win32, etc. Has some caveats with shared
libraries (essentially, you have to install the shared library in an
expected place as well as the executable).
Dan Pierson
Control Technology Corporation
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.