K
Kenjis Kaan
Would it be possible to move support files under
perl\site\lib\auto\... (DLLs, LIB, EXP etc) to another location
under your dev directory? I am developing perl applications that will
then be pushed down to end users PC as a package. I need to make this
package self contained so that when it sits on the client PC it can be
run right away. The problem is that there is only a basic Perl
installation on the end users PC with non of the fancy modules
installed. So I would like to be able to create my application in
such a way that I can put the DLLs/LIB of the package in the current
directory, as well as the module.pm itself. I wonder if perl will
allow you to do that. I notice whenever I install a package, it puts
all the DLLs,LIB files into the perl\site\lib\auto directory. I don't
want ot have to go and install various package on thousands of PCs
before an application can be run. There has to be a way so that you
can put the DLLs eg. DB_File.dll and DB_File.lib inside the current
development directory containing the codes I am developing. So when I
hand the complete product over to who ever use it, the thing will run
right away. You just can't expect end user to know how to install
perl packages.
perl\site\lib\auto\... (DLLs, LIB, EXP etc) to another location
under your dev directory? I am developing perl applications that will
then be pushed down to end users PC as a package. I need to make this
package self contained so that when it sits on the client PC it can be
run right away. The problem is that there is only a basic Perl
installation on the end users PC with non of the fancy modules
installed. So I would like to be able to create my application in
such a way that I can put the DLLs/LIB of the package in the current
directory, as well as the module.pm itself. I wonder if perl will
allow you to do that. I notice whenever I install a package, it puts
all the DLLs,LIB files into the perl\site\lib\auto directory. I don't
want ot have to go and install various package on thousands of PCs
before an application can be run. There has to be a way so that you
can put the DLLs eg. DB_File.dll and DB_File.lib inside the current
development directory containing the codes I am developing. So when I
hand the complete product over to who ever use it, the thing will run
right away. You just can't expect end user to know how to install
perl packages.