At 21:45 2002.05.19, Tim Musson wrote: >Hey Eric, > >My MUA believes you used QUALCOMM Windows Eudora Version 5.1 >to write the following on Sunday, May 19, 2002 at 9:09:31 PM. > >EB> To install CPAN modules on a W32 PC, you need to get a copy of >EB> nmake <ftp://ftp.microsoft.com/Softlib/MSLFILES/nmake15.exe>. > >EB> Then, all you have to do is: > >EB> perl Makefile.pl >EB> nmake >EB> nmake test >EB> nmake install > >EB> and you should be OK. > >thanks! That did most of it... Am I correct in assuming the html >documentation in the ActiveState distro is not updated by the above?
Glad it helped. No, the CPAN installation does not update the ActivePerl documentation. In fact, most of the CPAN modules do not come with an HTML doc. You have to use POD2HTML to generate it, put the HTML file in the perl\html directory and use ActivePerl::DocTools to generate a new HTML Table of Content. One way to read the doc for the CPAN module is to use perldoc -m <module name>. (e.g. perldoc -m File::Find). >Is there a document that describes what the above is doing? I did get >this output which is somewhat informative. I beleive you can find more information about make and nmake outputs on the sites where these tools are available. There is a whole O'Reiley book on make if you want to know the details. As for the ouput given when installing a CPAN module, I don't remember of any specific document off hand. I can tell you that perl Makefile.pl generate a "makefile" text file that is used by the nmake app. nmake wiithout parameter "build" the package. If compilation is needed, it compile etc. In the case of a Win32 PC, it mostly check for the other modules dependencies. It also put all the files in a special directory (blib) that will allow the module to be tested without being installed. nmake test run a series of test to see if the script would run properly in your environment. In your module example, the tests are not very elaborate. More and more, you will see very exhautive testing done. See IPC::Run for example. The one think you should remember is that you should not install a module that do not pass its tests. Sometimes, you will see tests that are skiped. This is not a faillure, it is just that these tests are flaged not to be run in your environment. You may still have a Pass result when some tests are skiped. This probably means that you can install but not all the functions will work. nmake install mostly copies the files were they need to be on your system to be used by perl. ><nmake commands + output> >>nmake > >Microsoft (R) Program Maintenance Utility Version 1.50 >Copyright (c) Microsoft Corp 1988-94. All rights reserved. > >cp PalmDoc.pm blib\lib\Pod\PalmDoc.pm > > <TimQ>This one seems fairly straight forward, copy a > file for use later.</TimQ> Yep. Copy in blib, not the "production" directory. The module is still not available for commun usage. >>nmake test > >Microsoft (R) Program Maintenance Utility Version 1.50 >Copyright (c) Microsoft Corp 1988-94. All rights reserved. > > D:\Perl\bin\perl.exe -Iblib\arch -Iblib\lib -ID:\Perl\lib -ID:\Perl\lib >test.pl >1..1 >ok 1 > > <TimQ>Testing to see of the install line will run?</TimQ> Yes, here it says that it should run on you PC. >>nmake install > >Microsoft (R) Program Maintenance Utility Version 1.50 >Copyright (c) Microsoft Corp 1988-94. All rights reserved. > >Installing D:\Perl\site\lib\Pod\PalmDoc.pm >Writing D:\Perl\site\lib\auto\Pod\PalmDoc\.packlist >Appending installation info to D:\Perl\lib/perllocal.pod > > <TimQ>Guess this is where I have the questions. > First line probabily copied from the location that was the > results of running 'nmake'. Why were the second and third > lines done? I did see *what* they did, but why?</TimQ> These two files keep track of the new module installed in your PC. The .packlist list all the files install for the Pod::PalmDoc module. The perllocal.pod keeps a log of all the installation done on your PC. You can do a perldoc d:\perl\lib\perllocal.pod to see that log. Hope this helps. ---------------------------------------------------------- Éric Beaudoin <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
