aquitaine

aquitaine has asked for the wisdom of the Perl Monks concerning the following question:

Well I'm developing some perl code and i need for it to be installed on some locations on servers accross the network. Thing is that a lot of the computers dont have perl and i cant install it there. So i want to compile from Perl into Binary.

I looked up perlcc and it works pretty fine for compiling some simple scripts. But in this case i have MySQL back end so i need to use the DBI module. When i use the DBI module i geta huge file that doesnt execute, with an error message like Cant locate method connect via package DBI line whatever...

I tried making the B:CC module, but that doesnt work out to well either since it involves having some perl.h and other header files that all the machines dont have.

What can I do to ensure that my code will run on machines where there is no perl interpretter ?
I'm at an end here would appreciate any help !
Cheers,
Aquitaine

Comment on aquitaine

Replies are listed 'Best First'.
Re: aquitaine by Beatnik (Parson) on Feb 12, 2001 at 03:35 UTC
Well, Perl2Exe is one way to do it, but building exotic modules could be a problem. Check this node for previous aggrivations :) Greetz Beatnik ... Quidquid perl dictum sit, altum viditur.	[reply]
(tye)Re: aquitaine by tye (Sage) on Feb 12, 2001 at 08:52 UTC
You can install scripts that you write but you can't install Perl? Why is that? The basic install of Perl is simply unzipping a directory tree that doesn't even take up that much space. If you want that install of Perl to be usable for building and installing modules, then you'll also need to update Config.pm to reflect where Perl was installed (which doesn't sound necessary in this case). If you want Perl in the PATH then you have to change the PATH, but since you won't be running a ton of scripts I'd just pl2bat each one and teach them to find perl even though it isn't in the PATH. - tye (but my friends call me "Tye")	[reply]