see. It is written in the POD format (see pod/perlpod.pod) which is
specifically designed to be readable as is.
-=head1 Name
+=head1 NAME
-Perl for NetWare
+perlnetware - Perl for NetWare
-=head1 Description
+=head1 DESCRIPTION
This file gives instructions for building Perl 5.7 and above, and also
Perl modules for NetWare. Before you start, you may want to read the
code distribution was extracted. Make sure you read and understand
the terms under which the software is being distributed.
-=head1 Build
+=head1 BUILD
This section describes the steps to be performed to build a Perl NLM
and other associated NLMs.
=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.
-
-=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.
-
-=item Custom Build Environment
+=item SetNWBld.bat
-If you want to change the default settings you could do so by
-following the steps listed below.
+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</now> will show the current settings and I</h>
-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
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
The make process also creates the Perl extensions as I<<Extension>.nlm>
-=head1 Install
+=head1 INSTALL
To install NetWare Perl onto a NetWare server, first map the Sys
volume of a NetWare server to I<i:>. This is because the makefile by
folder. The Perl interpreter, I<perl.nlm>, is copied under
I<sys:\perl\system> folder. Copy this to I<sys:\system> 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)
+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)
-=head1 Build new extensions
+=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
install> 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
+not copied. Thus one must first install Windows Perl, Then install
NetWare Perl.
Once this is done, do the following to build any extension:
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 *
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
+
+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 *
-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
-=head1 Acknowledgements
+=head1 ACKNOWLEDGEMENTS
The makefile for Win32 is used as a reference to create the makefile
for NetWare. Also, the make process for NetWare port uses
miniperl.exe to run scripts during the make and installation process.
-=head1 Authors
+=head1 AUTHORS
Anantha Kesari H Y (hyanantha@novell.com)
Aditya C (caditya@novell.com)
-=head1 Date
+=head1 DATE
=over 4
=item *
-Modified - 8 May 2002
+Modified - 28 May 2002
=back