C:\Perl\Site\Lib in general is the place where ActiveState Perl stores additional CPAN modules, whether the installation was done with PPM, CPAN(PLUS) or nmake install (i.e. by hand).
If there is any likelyhood of a name clash between your code and CPAN modules, you could get into hot water. It's also worth considering using the standard CPAN mechanism: ExtUtils::MakeMaker or Module::Build for packaging up your modules, even if you never intend to publish them onto CPAN. This will give you the benefit of a nice standard installation procedure, and a way of bundling unit tests with your modules. If you do this, you no longer need to know or care where nmake install puts the modules, as this is defined in your Perl installation.
See also:
--
Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ? (Missquoting Janis Joplin)
| [reply] |
You can create a directory like c:\perl\mylibs and set the PERL5LIB environment variable. You can then put your modules there and perl will find them. You can even create this directory on a shared device/network drive, so every machine in the network can access them without installation.
| [reply] [d/l] |
Just have to create a directory called like Error inside of the c:\perl\site\lib\ and place the module in there.
It can be called in the programs like,
Error::YourModule;
| [reply] |
| [reply] [d/l] |
| [reply] |