X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.netware;h=3dd70a6f4cbe4b827b01174c4ce599f2c4914e96;hb=ba92458f95420534d366ac8022adf95f17e5b19b;hp=1e795f3e84f8650e6f4ef0da02908c225010ff05;hpb=0cf85a069f041d1204f656444e4214a7b5fd4276;p=p5sagit%2Fp5-mst-13.2.git diff --git a/README.netware b/README.netware index 1e795f3..3dd70a6 100644 --- a/README.netware +++ b/README.netware @@ -33,58 +33,43 @@ 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. -=item * - -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 +=over 4 -If you want to change the default settings you could do so by following the steps listed -below. +=item SetNWBld.bat -=over 4 +The Execution of this file takes 2 parameters as input. The first +being the NetWare SDK path, second being the path for CodeWarrior +Compiler & tools. Execution of this file sets these paths and also +sets the build type to Release by default. =item Buildtype.bat -This sets the build type to release or debug. +This is used to set the build type to debug or release. Change the +build type only after executing SetNWBld.bat =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. - -=item SetNWBld.bat - -This sets the NetWare SDK path, path to Compiler & other tools. - -These batch files are under NetWare\bat folder. These batch files -call a couple of other batch files to setup the environment. Invoking -the batch file with I will show the current settings and I -or I gives the usage help. +Example: + 1. Typing "buildtype d on" at the command prompt causes the buildtype + to be set to Debug type with D2 flag set. + 2. Typing "buildtype d off" or "buildtype d" at the command prompt causes + the buildtype to be set to Debug type with D1 flag set. + 2. Typing "buildtype r" at the command prompt sets it to Release Build type. =back =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 +Currently the following two build types are tested on NetWare: =over 4 @@ -111,12 +96,13 @@ 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. @@ -124,17 +110,17 @@ Example: At the command prompt Type "nmake nwinstall". 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: @@ -153,7 +139,11 @@ Run the following command at the command prompt: Example: - perl -Ic:/perl/5.7.2/lib/NetWare-x86-multi-thread -Ic:\perl\5.7.2\lib MakeFile.pl + perl -Ic:/perl/5.6.1/lib/NetWare-x86-multi-thread -Ic:\perl\5.6.1\lib MakeFile.pl + +or + + perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread -Ic:\perl\5.8.0\lib MakeFile.pl =item * @@ -164,24 +154,28 @@ 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. 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 + perl -Ic:/perl/5.6.1/lib/NetWare-x86-multi-thread -Ic:\perl\5.6.1\lib MakeFile.pl INSTALLSITELIB=i:\perl\lib -=back +or + + perl -Ic:/perl/5.8.0/lib/NetWare-x86-multi-thread -Ic:\perl\5.8.0\lib MakeFile.pl + INSTALLSITELIB=i:\perl\lib -= 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 -without minor changes depending on the type of module. +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 without minor changes depending on the type of +module. =back @@ -214,6 +208,6 @@ Modified - 13 July 2001 =item * -Modified - 8 May 2002 +Modified - 28 May 2002 =back