On Tuesday, August 27, 2002, at 11:43 , Angerstein wrote:
[..]
> How can I compile a perlscript with all modules it use in 1 fine perl
> "bineary" program?
[..]
is your question:
how to get to a single executable binary image
of my perl "script", that will contain in it all
possible external references to perl modules - and
be the binary executable file that is opcode consistent
with the target host's OS/ARCH
cf perldoc perlcc
or what I think the question I am hearing you ask:
how do I get all of the supporting perl modules
delivered onto machines that do not have compilers.
the lack of compilers on the target host means that you
will need to 'compile' those modules that have XS components
and require a compiler - on a 'build machine' - where
there IS already a compiler for the OS/REV/ARCH that is
compatible. The dopiest trick we have all used then, is
to 'tarball' up that directory - as it sits - so that
one can unwrap the tarball and type
make install
which presumes that 'make' is installed on the machines.
It IS ugly - but it works.
a part of the problem with trying to take the perlcc
route is that it would presume that the perl modules
are already in place and compiled to be either static
or dynamic objects.... but I think if you are creative
about that you could probably work your way around it...
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
