Yuv,
As your wiki entry covers everything you need to install PAR::Packer, I
wondered if you might like to add the following to it to make it absolutely
complete.
The method described works for any ActivePerl 5.10 version.
For ActivePerl 5.8 versions it works for any build >= 820.
For ActivePerl builds < 820, the following additional action is required.
Install ExtUtils::FakeConfig >= 0.11 by downloading the source from CPAN and
doing:
perl Makefile.PL
dmake
dmake test
dmake install
When you come to build modules, you need to pass an extra option when running
Makefile.PL so that the method for building modules becomes:
perl -MConfig_m Makefile.PL
dmake
dmake test
dmake install
The ExtUtils::FakeConfig pod also points out you can set set PERL5OPT=-MConfig_m
However, the PAR::Packer build will fail if you use this option. For most
modules, either way of setting Config_m will work, but for a very few cases you
will find that only one of the methods work.
Regards
Mark
Yuval Levy wrote:
So, here is my promised write up - correct me if I am wrong:
<http://wiki.panotools.org/Install_Panotools-Script_on_Windows#Infrastructure_to_build_the_.exe_tools_-_the_new_way>
I went the MinGW way (thank you, Mark!).
Jan Dubois wrote:
Setting of ccversion will be done automatically (at runtime) in
ActivePerl build 823
(whenever 5.8.9 gets released) and in 1003 (probably out next week).
I may try this one at a later stage.
I would recommend using either VC++ 6 or MinGW to build Perl modules,
and especially
PAR binaries because these 2 compilers use MSVCRT.dll as the C runtime
library, and
this library is part of the OS, so there is no need to deploy it with
your application.
If you compile any module with VC 2008, then you will always have to
include MSVCR90.dll
with your applications too because it may not be present on a target
machine.
that's quite an important detail. can anybody explain to me why
Microsoft amputates its own O/S and does not include MSVCR90.dll?
and (correct me if my language is not precise, I'm a caveman) is there a
way to bring statically linked Perl modules that don't need any of these
dll?
the current ("legacy"/undocumented) way to ship compiled Perl modules
with hugin is to bundle perl58.dll. I see with great pleasure that this
is no longer necessary with PAR::Packer - my hello world test seems to
run without it?
thanks a lot again!
Yuv
