Re: Possible solution for Emdebian without perl?
I take it this is perl variant of Py2App or Py2Exe -- correct ??
Py2* actually wraps the python runtime, the python app (byte compiled),
the required python modules (byte compiled) and other required libraries
into a single 'executable' (a .app or .exe).
Presuming PP does something similar (correct/ignore me if I'm wrong -- I
don't do perl), then each perl application/script would have it's own
perl runtime, modules and libraries. If you had lots of perl
apps/scripts then you would have lots of copies of the the perl runtime,
and many of the common modules and libraries.
I that is correct, then would PP really be suitable for tightly embedded
systems ????
I find Py2App and Py2Exe suitable when you want to distribute
applications to end users that have varying host setups. You can
encapsulate all the dependent libraries and runtime progs into a single
app image and be confident that it will run on any machine, regardless
of what version of libraries and runtimes they may have installed on
their host.
The environment for an embedded system is a lot more controlled and is
generally not an issue.
I think a light weight perl installation is probably a better option --
either that or have binary or sh replacements for the perl scripts.
Hope I'm not barking up the wrong tree.
Brendan.
Neil Williams wrote:
> http://par.perl.org/wiki/Main_Page
>
> http://jackyf.livejournal.com/106217.html
>
> pp - Perl Packager
> Turn your Perl programs into ready-to-run executables
> Pack scripts and required libraries with a binary loader that runs the
> script Build dependent applications, which require an existing Perl
> installation on the target computer Build freestanding applications,
> which will run on a target computer that does not have Perl installed
> Optionally obfuscate your programs using InputFilters Tested on
> Windows, *BSD, Linux, Mac OS X, Cygwin, AIX, Solaris, HP-UX, OS/2...
> Put PAR files into @INC to avoid version conflicts Works with remote
> URL as well as local files Supports XS modules and DATA sections
>
> It's being tested with cupt, the perl replacement for apt - only now
> cupt itself could be usable without perl *or* apt. Hmmm....
>
> Next candidate: adduser & debconf . . .
>
>
Reply to: