Standalone applications

jurgen.defurne at philips.com jurgen.defurne at philips.com
Wed Feb 7 08:42:51 CET 2001


Basically, what you are trying to do here is the same that Clipper did way back.
THe minumum program we could get with it was 100kB. If it took the database
library and the advanced stuff, we got executables between 350kB and 700 kB.
What it did have, was that once most libraries were in it, the programs expanded
less rapid.

Does freeze compile everything to C and then to binary ? Shouldn't there
be a way that you can create an executable, which consists of two parts :
- the first part being code and libraries
- the second part a data part, which consists of all byte codes needed

Jurgen




paulus132 at my-deja.com@SMTP at python.org on 06/02/2001 17:03:11
Sent by:	python-list-admin at python.org
To:	python-list at python.org@SMTP
cc:	 
Subject:	Re: Standalone applications
Classification:	

In article <p6qlmrooik8.fsf at informatik.hu-berlin.de>,
  Martin von Loewis <loewis at informatik.hu-berlin.de> wrote:
> "Ryujin" <ryu-jin at bigfoot.com> writes:
>
> > Any suggestion???
>
> I personally prefer freeze. It requires a C compiler, but gives you
> best control and reliability. Plus it allows to create *truly*
> stand-alone binaries, i.e. binaries that are not even dependent on
> shared libraries.
>

I also have some good experience with freeze, but the binaries are big
(1.8M on Sun, 0.5M after strip), even for very simple *.py scripts !!

Do you have some tips to reduce it ??

Paul Perrin



> Regards,
> Martin
>


Sent via Deja.com
http://www.deja.com/
--
http://mail.python.org/mailman/listinfo/python-list






More information about the Python-list mailing list