From: Jarkko Hietaniemi Date: Mon, 27 May 2002 18:15:32 +0000 (+0000) Subject: POD cleanup and rewrapping. X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=79b683f6279382b62e7d80464271026fcfc32a23;p=p5sagit%2Fp5-mst-13.2.git POD cleanup and rewrapping. p4raw-id: //depot/perl@16817 --- diff --git a/README.netware b/README.netware index 1e795f3..f453086 100644 --- a/README.netware +++ b/README.netware @@ -33,25 +33,25 @@ The build process is dependent on the location of the NetWare SDK. Once the Tools & SDK are installed, the build environment has to be setup. The following batch files setup the environment. +=over 4 + =item * -If you want to build with Default settings you can follow the One step process given below -to create the default Build Environment. +If you want to build with Default settings you can follow the One step +process given below to create the default Build Environment. =item SetNWDef.bat -The Execution of this file takes 2 parameters as input.The first being the NetWare SDK path, -Second being the path for CodeWarrior Compiler & other tools. Execution of this file -sets the Build type to Release(default) , the NetWare SDK path, path for Compiler & other tools. - -=back - -=item * Custom Build Environment +The Execution of this file takes 2 parameters as input.The first being +the NetWare SDK path, Second being the path for CodeWarrior Compiler & +other tools. Execution of this file sets the Build type to +Release(default) , the NetWare SDK path, path for Compiler & other +tools. -If you want to change the default settings you could do so by following the steps listed -below. +=item Custom Build Environment -=over 4 +If you want to change the default settings you could do so by +following the steps listed below. =item Buildtype.bat @@ -59,8 +59,9 @@ This sets the build type to release or debug. =item * -Example: Typing "buildtype d on" at the command prompt causes the buildtype to be set to Debug type. - Typing "buildtype r" at the command prompt sets it to Release Build type. +Example: Typing "buildtype d on" at the command prompt causes the +buildtype to be set to Debug type. Typing "buildtype r" at the +command prompt sets it to Release Build type. =item SetNWBld.bat @@ -75,14 +76,14 @@ or I gives the usage help. =head2 Make -The make process runs only under WinNT shell. -The NetWare makefile is located under the NetWare folder. -This makes use of miniperl.exe to run some of -the Perl scripts. To create miniperl.exe, first set the required paths for -Visual c++ compilier (specify vcvars32 location) at the command prompt. -Then run nmake from win32 folder through WinNT command prompt. -The build process can be stopped after miniperl.exe is created. Then run nmake -from NetWare folder through WinNT command prompt. +The make process runs only under WinNT shell. The NetWare makefile is +located under the NetWare folder. This makes use of miniperl.exe to +run some of the Perl scripts. To create miniperl.exe, first set the +required paths for Visual c++ compilier (specify vcvars32 location) at +the command prompt. Then run nmake from win32 folder through WinNT +command prompt. The build process can be stopped after miniperl.exe +is created. Then run nmake from NetWare folder through WinNT command +prompt. Currently the following two build types are tested on NetWare @@ -111,30 +112,30 @@ The make process also creates the Perl extensions as I<.nlm> =head1 Install -To install NetWare Perl onto a NetWare server, first map the Sys volume -of a NetWare server to I. This is because the makefile by default -sets the drive letter to I. Type I from NetWare folder -on a WinNT command prompt. This will copy the binaries and module files -onto the NetWare server under I folder. The Perl interpreter, I, -is copied under I folder. Copy this to I folder. +To install NetWare Perl onto a NetWare server, first map the Sys +volume of a NetWare server to I. This is because the makefile by +default sets the drive letter to I. Type I from +NetWare folder on a WinNT command prompt. This will copy the binaries +and module files onto the NetWare server under I +folder. The Perl interpreter, I, is copied under +I folder. Copy this to I folder. -Example: At the command prompt Type "nmake nwinstall". - This will install NetWare Perl on the NetWare Server. - Similiarly if you type "nmake install", - This will cause the binaries to be installed on the local machine. - (Typically under the c:\perl folder) +Example: At the command prompt Type "nmake nwinstall". This will +install NetWare Perl on the NetWare Server. Similarly if you type +"nmake install", This will cause the binaries to be installed on the +local machine. (Typically under the c:\perl folder) - =head1 Build new extensions To build extensions other than standard extensions, NetWare Perl has -to be installed on Windows along with Windows Perl. The Perl for Windows can be -either downloaded from the CPAN site and built using the sources, or the binaries -can be directly downloaded from the ActiveState site. -Installation can be done by invoking I from the NetWare folder -on a WinNT command prompt after building NetWare Perl by following steps given above. -This will copy all the *.pm files and other required files. -Documentation files are not copied.Thus one must first install Windows Perl, Then install +to be installed on Windows along with Windows Perl. The Perl for +Windows can be either downloaded from the CPAN site and built using +the sources, or the binaries can be directly downloaded from the +ActiveState site. Installation can be done by invoking I from the NetWare folder on a WinNT command prompt after +building NetWare Perl by following steps given above. This will copy +all the *.pm files and other required files. Documentation files are +not copied.Thus one must first install Windows Perl, Then install NetWare Perl. Once this is done, do the following to build any extension: @@ -164,9 +165,9 @@ nmake nmake install Install will copy the files into the Windows machine where NetWare -Perl is installed and these files may have to be copied to the NetWare server -manually. Alternatively, pass I as an -input to makefile.pl above. Here I is the mapped drive to the +Perl is installed and these files may have to be copied to the NetWare +server manually. Alternatively, pass I as +an input to makefile.pl above. Here I is the mapped drive to the sys: volume of the server where Perl on NetWare is installed. Now typing I, will copy the files onto the NetWare server. @@ -175,9 +176,7 @@ Example: You can execute the following on the command prompt. perl -Ic:/perl/5.7.2/lib/NetWare-x86-multi-thread -Ic:\perl\5.7.2\lib MakeFile.pl INSTALLSITELIB=i:\perl\lib -=back - -= item * +=item * Note: Some modules downloaded from CPAN may require NetWare related API in order to build on NetWare.Other modules may however build smoothly with or